From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: dewar@adacore.com, Wiljan.Derks@zonnet.nl, gdb@sourceware.org
Subject: Re: How to tell gdb about dlls using remote protocol
Date: Wed, 07 Feb 2007 21:47:00 -0000 [thread overview]
Message-ID: <200702072147.l17LlbVU013575@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070202173456.GT17864@adacore.com> (message from Joel Brobecker on Fri, 2 Feb 2007 09:34:56 -0800)
> Date: Fri, 2 Feb 2007 09:34:56 -0800
> From: Joel Brobecker <brobecker@adacore.com>
>
> > Hmm, perhaps it successfully gets you out and only misses frames. I'm
> > pretty sure I remember that when debugging a Windows build of GDB, the
> > select helper threads live somewhere in NTDLL without a valid frame.
>
> I am not sure about that particular thread. But for the other ones,
> we are indeed counting on the fact that all we lose is skipping one
> frame.
>
> > I'd be curious to see it, at least, but I'm not sure what we can do.
>
> Here it is. The diff is probably malformed, because I had to remove
> a couple of patches we backported from head, but that should give
> you the idea.
I wouldn't be too thrilled to have this Windows-specific code in the
generic i386-tdep.c.
next prev parent reply other threads:[~2007-02-07 21:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 21:08 Wiljan Derks
2007-01-31 22:31 ` Daniel Jacobowitz
2007-02-01 17:52 ` Joel Brobecker
2007-02-01 22:54 ` Daniel Jacobowitz
2007-02-01 23:02 ` Joel Brobecker
2007-02-01 23:59 ` Daniel Jacobowitz
2007-02-02 6:20 ` Robert Dewar
2007-02-02 11:43 ` Daniel Jacobowitz
2007-02-02 16:51 ` Joel Brobecker
2007-02-02 16:56 ` Daniel Jacobowitz
2007-02-02 17:34 ` Joel Brobecker
2007-02-05 20:34 ` Wiljan Derks
2007-02-05 21:21 ` Joel Brobecker
2007-02-07 21:47 ` Mark Kettenis [this message]
2007-02-07 22:14 ` Mark Kettenis
2007-02-07 22:17 ` Daniel Jacobowitz
2007-02-08 21:14 ` Mark Kettenis
2007-02-08 23:00 ` Daniel Jacobowitz
2007-02-14 8:51 ` Joel Brobecker
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=200702072147.l17LlbVU013575@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=Wiljan.Derks@zonnet.nl \
--cc=brobecker@adacore.com \
--cc=dewar@adacore.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