From: Daniel Jacobowitz <drow@false.org>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: HW Watchpoint events and the inferior
Date: Thu, 02 Aug 2007 17:16:00 -0000 [thread overview]
Message-ID: <20070802171558.GA31488@caradoc.them.org> (raw)
In-Reply-To: <1185988407.4992.4.camel@localhost>
On Wed, Aug 01, 2007 at 02:13:27PM -0300, Luis Machado wrote:
> Yes, in fact i'm looking forward to improve that situation. That's
> why i'm going through some of the inferior handling
> code. Unfortunatelly there isn't much documentation there, and
> sometimes it gets rather bleak as to what GDB is really trying to
> do, and how it would handle multiple traps.
It's not sensible to ask how GDB handles this sort of thing, until it
actually does. Did you mean how it _should_ handle it?
Are you starting from Jan's patches? If not, why did you decide not
to? I have been assuming that it would be a simple matter of merging
them.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-08-02 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 15:23 Luis Machado
2007-08-01 16:00 ` Daniel Jacobowitz
2007-08-01 17:13 ` Luis Machado
2007-08-02 17:16 ` Daniel Jacobowitz [this message]
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=20070802171558.GA31488@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.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