On Wed, Dec 31, 2003 at 10:37:29AM -0500, Robert Baruch wrote: >Christopher Faylor wrote: >>The core dump occurred in a function which does not have a frame >>pointer. This screws up stack dumps on x86 systems. There isn't >>really much that you can do about this. > >Thanks for the reply. I guess what I don't understand is, if I don't >set error_start to dumper, I get what appears to be a nice stack trace >in the t.exe.stackdump file:
It's an unfortunate side effect of the way dumper works. The dumping process is paused waiting for a debugger (in this case dumper.exe) to connect. The routine that is used to pause is frameless. The stack is still available for inspection via something like 'x/100x $esp' but the stack trace is often munged in this scenario. -- 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/
