From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20040913

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:

(gdb) bt
#0  0x0850cce1 in kill ()
#1  0x0853e69c in raise ()
#2  0x00000006 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(gdb)

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):
gdb-t.0post-0.20040223.19

How reproducible:
Sometimes

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.

2.
3.
    

Additional info: