Re: C function

Maria Wilson (m.l.wilson@larc.nasa.gov) wrote: : We have call tech support and have an open case with them but they : cannot seem to figure out the problem either! Anybody out there have : any ideas? You are developing a shared library, so the appropriate thing to do is to use a symbolic debugger (gdb is really good, dbx is OK) and attach to the server process to look at what's going on. onstat -g glo - look for the proc id of the CPU VP gdb `which oninit` -p PROC_ID (the argument order might not be perfect). (Make sure you're compiling your library with the -g flag so that the symbol headers are still attached to the shared library). Then run your function. It should barf at the right place. Or set a trace-point at the function and step through it in the normal way. You might also want to read http://www.informix.com/idn for a wealth of tips and techniques for 'C' development. It's not easy, but its very rewarding. KR Pb