From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org, gdb@sourceware.org
Subject: Re: [rfc / remote protocol] Remote shared library events
Date: Fri, 18 May 2007 16:10:00 -0000 [thread overview]
Message-ID: <20070518160952.GA27839@caradoc.them.org> (raw)
In-Reply-To: <m3r6pe9kym.fsf@codesourcery.com>
On Fri, May 18, 2007 at 09:04:49AM -0700, Jim Blandy wrote:
> Sorry --- of course the @var{r} associated with the dllstop isn't
> meaningless. Regarding the other pairs, I didn't realize that one
> wanted expedited registers for DLL events; would we actually use them?
Sure. For instance, if stop-on-solib-events was set, we would stop;
or if we were single-stepping multiple instructions we'd (I hope, I
haven't tested this) keep stepping.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-05-18 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 20:16 Daniel Jacobowitz
2007-05-09 20:40 ` Smith, Stephen (SWCOE)
2007-05-10 3:18 ` Eli Zaretskii
2007-05-16 22:59 ` Jim Blandy
2007-05-18 0:27 ` Daniel Jacobowitz
2007-05-18 16:04 ` Jim Blandy
2007-05-18 16:10 ` Daniel Jacobowitz [this message]
2007-05-18 16:49 ` Jim Blandy
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=20070518160952.GA27839@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.com \
/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