From: Eli Zaretskii <eliz@gnu.org>
To: Gordon Prieur <Gordon.Prieur@Sun.COM>
Cc: gdb@sourceware.org
Subject: Re: Strange stack trace on Windows
Date: Sun, 30 Sep 2007 18:13:00 -0000 [thread overview]
Message-ID: <uk5q8bp8j.fsf@gnu.org> (raw)
In-Reply-To: <46FEC75E.9010207@Sun.COM> (message from Gordon Prieur on Sat, 29 Sep 2007 14:45:02 -0700)
> 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.
next prev parent reply other threads:[~2007-09-30 7:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 22:01 Gordon Prieur
2007-09-30 3:00 ` Daniel Jacobowitz
2007-09-30 18:13 ` Eli Zaretskii [this message]
2007-10-01 14:03 ` Gordon Prieur
2007-10-01 14:39 ` Joel Brobecker
2009-03-17 11:58 Roland Schwingel
2009-03-17 13:19 ` Joel Brobecker
2009-03-17 13:49 Roland Schwingel
2009-03-17 14:27 ` Pedro Alves
2009-03-17 15:08 ` Joel Brobecker
2009-03-17 15:26 Roland Schwingel
2009-03-17 15:39 Roland Schwingel
2009-03-17 19:43 ` Joel Brobecker
2009-03-18 9:26 Roland Schwingel
2009-03-19 14:18 ` Joel Brobecker
2009-03-23 13:12 Roland Schwingel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uk5q8bp8j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Gordon.Prieur@Sun.COM \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox