On Sun, Jul 05, 2009 at 05:21:50PM +0100, Roman Werpachowski wrote: >On Sun, Jul 5, 2009 at 1:50 PM, Dave Korn<XXXX> wrote: >> ?Well, what happened was that there's a bug somewhere, and while cygwin was >> in the process of dumping the stack trace for the abort caused by your >> assertion firing, > >One more question: how can I use this stack trace to debug genuine >errors? "gdb -c" cannot load it.
The stack dump is for human consumption. gdb doesn't know anything about it. You can look up the addresses in gdb by doing something like: (gdb) l *0xf00f00fa Or you can use addr2line. If you want a real core dump see: http://www.cygwin.com/cygwin-ug-net/using-utils.html#dumper cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
