core dump, please help! [message #36867] |
Fri, 28 December 2001 06:01 |
Nina
Messages: 113 Registered: March 2000
|
Senior Member |
|
|
My Pro*C core dumps with a segmentation fault error. I was wondering if anyone knows a way to analyze the core dump file. More specifically: how to do a trace back of the core file in oder to get a stack trace or any sort of meaningful analysis?
Also, any tips on debugging a pro*c memory leak problem?
THANK YOU IN ADVANCE
----------------------------------------------------------------------
|
|
|
Re: core dump, please help! [message #37664 is a reply to message #36867] |
Tue, 19 February 2002 12:49 |
Mike
Messages: 417 Registered: September 1998
|
Senior Member |
|
|
Got the same thing today - sig 11. Not an expert, but you can try "strings core" and redirect to a file. Look thru here, especially at the end. Takes a while, and most stuff is not relevant, but the bugs usually show up (worked for me). Someone showed me you can use gdb to look at the call stack, and this was very useful, too. Determine exe that bombed. Go to location of core file. If file is named simply 'core', enter "gdb <fullpathname of exe> core". At 'gbd' prompt, enter 'ba'. Look at stack for offending module. Good luck!
|
|
|