From: "Eli Zaretskii" <eliz@gnu.org>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: drow@false.org, cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Watchpoints per thread patch
Date: Thu, 28 Oct 2004 04:55:00 -0000 [thread overview]
Message-ID: <01c4bca9$Blat.v2.2.2$adcffb00@zahav.net.il> (raw)
In-Reply-To: <418022DE.204@redhat.com> (message from Jeff Johnston on Wed, 27 Oct 2004 18:36:14 -0400)
> Date: Wed, 27 Oct 2004 18:36:14 -0400
> From: Jeff Johnston <jjohnstn@redhat.com>
> Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
>
> The attached patch is the rework of my original attempt. It no longer uses
> configuration or magic defines. Per Mark's suggestion, it uses an observer to
> handle inserting watchpoints on a new thread and only the low-level code knows
> about inserting/removing watchpoints on all threads.
>
> Ok to commit?
A few comments:
> +/* External function to insert all existing watchpoints on a newly
> + attached thread. IWPFN is a callback function to perform
> + the target insert watchpoint. This function is used to support
> + platforms whereby a watchpoint must be inserted/removed on each
> + individual thread (e.g. ia64-linux and s390-linux). For
> + ia64 and s390 linux, this function is called via a new thread
> + observer. */
In this comment, the word "whereby" should be replaced by "where", I
think.
> --- target.h 8 Oct 2004 20:29:55 -0000 1.65
> +++ target.h 27 Oct 2004 21:43:51 -0000
> @@ -178,6 +178,15 @@ extern char *target_signal_to_name (enum
> /* Given a name (SIGHUP, etc.), return its signal. */
> enum target_signal target_signal_from_name (char *);
> \f
> +
> +/* Watchpoint specification. */
> +struct target_watchpoint
> + {
> + CORE_ADDR addr;
> + int len;
> + int type;
> + };
> +
Why do we put on target.h, which is a general header, a definition of
a struct used only on certain platforms?
> --- doc/observer.texi 1 Sep 2004 17:59:37 -0000 1.8
> +++ doc/observer.texi 27 Oct 2004 21:43:51 -0000
> @@ -95,3 +95,7 @@ inferior, and before any information on
> The specified shared library has been discovered to be unloaded.
> @end deftypefun
>
> +@deftypefun void new_thread (ptid_t @var{ptid})
> +A new thread has been attached to.
"A new thread has been attached" to what? The description of the
observer should at least reference the argument @var{ptid}.
next prev parent reply other threads:[~2004-10-28 4:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 23:57 Jeff Johnston
2004-10-20 5:04 ` Eli Zaretskii
2004-10-20 11:03 ` Mark Kettenis
2004-10-20 16:21 ` Jeff Johnston
2004-10-20 17:27 ` Andrew Cagney
2004-10-20 17:30 ` Daniel Jacobowitz
2004-10-27 22:36 ` Jeff Johnston
2004-10-27 22:41 ` Daniel Jacobowitz
2004-10-27 23:17 ` Jeff Johnston
2004-10-28 13:33 ` Daniel Jacobowitz
2004-10-28 19:47 ` Jeff Johnston
2004-10-28 19:52 ` Daniel Jacobowitz
2004-10-28 20:13 ` Jeff Johnston
2004-10-28 4:55 ` Eli Zaretskii [this message]
2004-11-04 18:25 ` Jeff Johnston
2004-11-04 21:21 ` Eli Zaretskii
2004-11-05 4:49 ` Daniel Jacobowitz
2004-11-05 16:52 ` Andrew Cagney
2004-11-05 18:29 ` Daniel Jacobowitz
2004-11-08 21:33 ` Andrew Cagney
2004-11-09 1:04 ` Daniel Jacobowitz
2004-11-09 2:20 ` Andrew Cagney
2004-11-09 2:33 ` Daniel Jacobowitz
2004-11-09 4:53 ` Eli Zaretskii
2004-11-09 15:11 ` Andrew Cagney
2004-11-09 18:41 ` Daniel Jacobowitz
2004-11-11 21:22 ` Andrew Cagney
2004-11-09 19:06 ` Jeff Johnston
2004-11-09 19:31 ` Daniel Jacobowitz
2004-11-09 20:24 ` Jim Blandy
2004-11-10 0:02 ` Jeff Johnston
2004-11-10 14:39 ` Jim Blandy
2004-11-11 21:23 ` Andrew Cagney
2004-11-09 20:48 ` Jeff Johnston
2004-11-09 20:50 ` Daniel Jacobowitz
2004-11-10 19:45 ` Eli Zaretskii
2004-11-10 22:08 ` Jeff Johnston
2004-11-10 19:43 ` Eli Zaretskii
2004-10-20 19:27 ` Eli Zaretskii
2004-11-05 11:49 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='01c4bca9$Blat.v2.2.2$adcffb00@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@redhat.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