Red Hat Bugzilla – Bug 137240
gdb cannot always backtrace through signal handler
Last modified: 2007-11-30 17:10:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
My program catches SIGSEGV (and similar) and prints out
a small bit of debugging before it asserts to create a core
file. On RedHat9 I can use gdb to backtrace through the
signal call back to the method that caused the original SIGSEGV,
but with FC2, I get this instead:
#0 0x0850cce1 in kill ()
#1 0x0853e69c in raise ()
#2 0x00000006 in ?? ()
Previous frame inner to this frame (corrupt stack?)
The actual bug that caused this core was a de-reference of
a null pointer to an object, ie:
MyObject foo* = NULL;
foo->something(); // Crashes
The code is compiled with -O2 and -g, among other flags.
The kernel is 2.6.9 + my networking patches.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. It is reproducible every time with my big, proprietary app. It is
not reproducible with a very simple test case. I can provide the core
file and executable if that helps.
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
this was fixed, seems to work in FC5 at least.