This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Strange stack trace on Windows
- From: Gordon Prieur <Gordon dot Prieur at Sun dot COM>
- To: gdb at sourceware dot org
- Date: Sat, 29 Sep 2007 14:45:02 -0700
- Subject: Strange stack trace on Windows
Hi,
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
Its not that I'm looking at the wrong thread, I've checked all threads
(and set the current thread to the user thread). Can anybody explain
this and
tell me how to get to user data?
Thanks,
Gordon