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: Wed, 01 Aug 2007 16:00:00 -0000 [thread overview]
Message-ID: <20070801160027.GA28305@caradoc.them.org> (raw)
In-Reply-To: <1185981481.5248.11.camel@localhost>
On Wed, Aug 01, 2007 at 12:18:01PM -0300, Luis Machado wrote:
> Folks,
>
> I've been investigating watchpoints on GDB and i have a question on how
> GDB handles Hardware Watchpoint events and which TID it uses to grab
> information about the stopped_data_address, considering a multithreaded
> application.
GDB does not contain support for watchpoints in multi-threaded
programs. You can find several patches and discussions of this issue
in the list archives as recently as the end of June.
In reply to a message from you, in fact!
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-08-01 16:00 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 [this message]
2007-08-01 17:13 ` Luis Machado
2007-08-02 17:16 ` Daniel Jacobowitz
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=20070801160027.GA28305@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