Re: Part II: Revenge of the CoreDumps

I'm not terribly familiar with how 4GL compiles, but sooner or later, there's a script called (c4gl?) that shells out to 'cc' (the C compiler). If you can edit this script to add a '-g' flag to the cc command line, that will include debugger information in the executable. Once that's been done, you can debug as follows (using the Solaris debugger as an example): $ adb <executable> <corefile> -- Start up the debugger adb> $c -- Print a call trace <output> adb> $q -- Quit The <output> given above will tell you (at minimum) the name of the function that caused the core dump. This should help you narrow down where in the code it's dying. HTH, - Tom Girsch Carlson@WHSmith wrote in message <364B1254.899@bellsouth.net>... >SaTriGuy wrote: >> >> If the program is a compiled program, and is producing a core file, then you >> can start by getting the stack trace from the core file. This can be done by >> using xdb and/or adb. This should help in the resolution of the problem. >> >> What is the case number?? > >#789609 > >How do I need to compile a 4gl in order to use a debugger? I know that >I can't STRIP the executable, as I do now. > >BTW, a clean run today at 10:30 in cron. I reset the cron to take place >at 6:30AM tomorrow, just to see what happens. > > > >John Carlson >Informix DBA >WHSmith USA Travel Retail