This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug debug/24490] [4.1 Regression] gcc / gdb backtrace problem



------- Comment #3 from kev dot gilbert at cdu dot edu dot au  2005-10-23 22:13 -------
Just for the record, I've pasted the incorrect gdb output for the second
backtrace. It is as follows:

#0  0x00240402 in __kernel_vsyscall ()
#1  0x00726118 in raise () from /lib/libc.so.6
#2  0x00727888 in abort () from /lib/libc.so.6
#3  0x0804839d in main (argc=1, argv=0xbfa69a14) at office/test.c:4

Sorry. And, yes, I should have added the OS & hardware platform. Noted for
future reference.


-- 

kev dot gilbert at cdu dot edu dot au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kev dot gilbert at cdu dot
                   |                            |edu dot au


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24490


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]