Programming

Thank you very much for your help Shamrock. I'm afraid I have to leave now as 17:30 in UK and have to get somewhere else on time.

Once again thank you - Mike

What errors are you getting with the new version...post them here please.

The server program I am linking, when executed is spawned from an IDL client program. THe client opens a two way pipe using STDIN and STDOUT to communicate. The IDL client issues command strings to the server and the server responds; data passes both ways, as do return codes. I follow every call to an API routine with a status code returned to the client. One dissadvantage of the pipe is that messages issued by the API on STDOUT go down the pipe rather than to the terminal.

To get round this Status codes that I send down the pipe are always preceded by the CHR(2) which I can look for as the start of what I have sent and I read away any "extraneous" messages preceding my status code and my associated message. In debug I can access the extraneous message that is usually just read away.

In this case however I call an API routine (with a debug print before it) and it never returns from the call, the server apparently terminates gracefully, and no message is issued either to STDOUT or STDERR.

Use gdb to debug runtime errors like the one you are facing...run the server program within a debugger and see it that helps any bit.

Shamrock and vgersh99 Thank you for all the help.

In the end I started with my original makefile and made incremental edits, checking that at each stage I got a successful result. At the end of that process I have a makefile that works; nothing went wrong. I admit that I still do not know what was wrong with my first attempt that was edited all in one big hit, but don't have the time to look at it further. This does not mean that I do not appreciate the time that you have spent; on the contrary I am most grateful.

Mike