From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Multi-threaded watchpoints, GNU/Linux native bits
Date: Mon, 01 Oct 2007 00:23:00 -0000 [thread overview]
Message-ID: <20071001002303.GB15835@caradoc.them.org> (raw)
In-Reply-To: <1190038504.4651.30.camel@localhost>
On Mon, Sep 17, 2007 at 11:15:04AM -0300, Luis Machado wrote:
> Quick comment:
>
> "CORE_ADDR *addr_p" right below "siginfo_p" should be eliminated since
> we're already getting that parameter from the function call.
Thanks. I checked it in with that change.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-01 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 18:57 Daniel Jacobowitz
2007-09-17 14:15 ` Luis Machado
2007-10-01 0:23 ` Daniel Jacobowitz [this message]
2007-10-02 16:42 ` Ulrich Weigand
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=20071001002303.GB15835@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@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