This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: seg fault produces stackdump with no stack trace
Steve Waldo wrote:
> Even the debugger didn't know where it was anymore! It's obvious in this case
> why it went off in the weeds, but I would have thought the stack would still
> be accessible.
Well of *course* the debugger doesn't know what 0x00000000 is because
that is not a valid program location. But it can give you a backtrace,
you're just not asking for it:
$ gdb --quiet a.exe
(gdb) r
[New thread 2912.0x544]
[New thread 2912.0xaf0]
Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x00401052 in letsCrash () at tc.c:4
#2 0x00401083 in main () at tc.c:9
(gdb)
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/