This is the mail archive of the gdb@sourceware.org mailing list for the GDB 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]

Re: Strange stack trace on Windows


Eli Zaretskii wrote: 
Date: Sat, 29 Sep 2007 14:45:02 -0700
From: Gordon Prieur <Gordon.Prieur@Sun.COM>

    When I interrupt the debugee on Windows I almost never get a stack trace
with he debuggee information in it. I get similar traces with both MinGW and
Cygwin gdb commands:

115where
115&"where\n"
115~"#0 0x7c90eb94 in ntdll!LdrAccessResource ()\n"
115~" from C:\\WINDOWS\\system32\\ntdll.dll\n"
115~"#1 0x7c90e3ed in ntdll!ZwRequestWaitReplyPort ()\n"
115~" from C:\\WINDOWS\\system32\\ntdll.dll\n"
115~"#2 0x7c9132f8 in ntdll!CsrProbeForWrite () from C:\\WINDOWS\\system32\\ntdll.dll\n"
115~"#3 0x00003fec in ?? ()\n"
115~"#4 0x0022fa70 in ?? ()\n"
115~"#5 0x0022fa70 in ?? ()\n"
115~"#6 0x00000000 in ?? ()\n"
115^done

If you type "step" repeatedly, do you eventually get to a frame that
is in your program? If you do, you can get a valid stack trace at
that point.

Sometime yes, sometimes no. I implemented that solution abotu 6 months ago but backed
it out because it was just as likely to crash gdb:-( or hang my IDE (netbeans).

Gordon

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