From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc, rfa/doc] Multi-threaded watchpoint improvements
Date: Thu, 17 Apr 2008 14:53:00 -0000 [thread overview]
Message-ID: <20080417123455.GA25679@caradoc.them.org> (raw)
In-Reply-To: <jetzi0st9c.fsf@sykes.suse.de>
On Thu, Apr 17, 2008 at 11:52:31AM +0200, Andreas Schwab wrote:
> Looking closer, it is actually a kernel bug. PTRACE_GETSIGINFO is not
> emulated for 32-bit processes, so that si_addr is set to the upper half
> of the address, which is of course zero.
Glad you could track that down. Yes, my patch made GDB less tolerant
of targets which claim they can report the stopped data address, but
actually fail. It will only report watchpoints when the target
doesn't know what address has changed, or report a changed address
that falls on a particular watchpoint. This lets us keep track of
which thread hit each watchpoint.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-17 12:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 18:40 Daniel Jacobowitz
2007-09-22 9:03 ` Eli Zaretskii
2007-09-22 14:04 ` Daniel Jacobowitz
2007-09-22 14:13 ` Eli Zaretskii
2007-09-22 15:37 ` Daniel Jacobowitz
2007-09-22 15:46 ` Eli Zaretskii
2007-09-22 18:28 ` Daniel Jacobowitz
2007-10-01 0:20 ` Daniel Jacobowitz
2007-10-24 14:59 ` Luis Machado
2007-10-24 16:00 ` Daniel Jacobowitz
2007-10-24 16:42 ` Luis Machado
2007-10-24 16:51 ` Daniel Jacobowitz
2007-10-24 18:08 ` Luis Machado
2007-10-24 18:20 ` Daniel Jacobowitz
2008-04-16 22:57 ` Andreas Schwab
2008-04-16 23:05 ` Daniel Jacobowitz
2008-04-16 23:18 ` Andreas Schwab
2008-04-17 0:25 ` Daniel Jacobowitz
2008-04-17 9:52 ` Andreas Schwab
2008-04-17 9:59 ` Andreas Schwab
2008-04-17 10:17 ` Andreas Schwab
2008-04-17 14:53 ` Daniel Jacobowitz [this message]
2008-04-20 2:35 ` Andreas Schwab
2008-04-23 11:55 ` Andreas Schwab
2008-04-23 19:46 ` Eli Zaretskii
2008-05-01 19:30 ` Daniel Jacobowitz
2008-05-01 19:50 ` Luis Machado
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=20080417123455.GA25679@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