From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 0/1] Threaded Watchpoints
Date: Mon, 10 Sep 2007 17:56:00 -0000 [thread overview]
Message-ID: <1189446990.4318.21.camel@localhost> (raw)
In-Reply-To: <20070910154443.GA10167@caradoc.them.org>
Hi,
> If that doesn't help, could you show me the error message? Thanks.
Yes, that does it, though it doesn't look right to have that definition
moved to "linux-nat.c". But i might have outdated include files (when
were they changed?), so the current code should be fine except for this
particular piece:
==== code ====
static int
-ppc_linux_stopped_by_watchpoint (void)
+ppc_linux_stopped_data_address (struct target_ops *target, CORE_ADDR
*addr_p)
{
- int tid;
- struct siginfo siginfo;
- ptid_t ptid = inferior_ptid;
+ struct siginfo *siginfo_p;
CORE_ADDR *addr_p;
- tid = TIDGET(ptid);
- if (tid == 0)
- tid = PIDGET (ptid);
=== code ===
We should get rid of the locally-defined "addr_p" since it's already
being passed as a parameter by "stopped_data_address".
I've built GDB, tried to insert a watchpoint after creating 10 threads
and the those threads triggered correctly.
As for the testcases, since PPC only supports one hardware watchpoint
per process, we should work that test case in a different way or mark it
as unsupported for PPC and write a different test case.
Regards,
--
Luis Machado
IBM Linux Technology Center
e-mail: luisgpm@linux.vnet.ibm.com
next prev parent reply other threads:[~2007-09-10 17:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 13:51 Luis Machado
2007-08-20 17:33 ` Luis Machado
2007-08-20 17:40 ` Luis Machado
2007-09-05 2:04 ` Daniel Jacobowitz
2007-09-05 12:31 ` Luis Machado
2007-09-10 0:21 ` Daniel Jacobowitz
2007-09-10 15:34 ` Luis Machado
2007-09-10 15:44 ` Daniel Jacobowitz
2007-09-10 17:56 ` Luis Machado [this message]
2007-09-10 18:30 ` Daniel Jacobowitz
2007-09-10 18:23 ` Ulrich Weigand
2007-09-10 18:29 ` Daniel Jacobowitz
2007-09-10 18:44 ` Ulrich Weigand
2007-09-10 18:54 ` Daniel Jacobowitz
2007-09-10 19:03 ` Ulrich Weigand
2007-09-10 19:12 ` Daniel Jacobowitz
2007-09-10 19:31 ` Mark Kettenis
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=1189446990.4318.21.camel@localhost \
--to=luisgpm@linux.vnet.ibm.com \
--cc=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