Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] GDB patches for hw watchpoints
Date: Wed, 17 Aug 2005 18:46:00 -0000	[thread overview]
Message-ID: <u8xz02z7k.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0508171223330.4564@lazy> (message from Manoj Iyer on Wed, 17 Aug 2005 12:27:46 -0500 (CDT))

> Date: Wed, 17 Aug 2005 12:27:46 -0500 (CDT)
> From: Manoj Iyer <manjo@austin.ibm.com>
> 
> 
> I am submitting this patch on behalf of  Ben Elliston <bje@au1.ibm.com>,
> this patch implements hardware watchpoints on PPC platform. Please review
> and comment, so I can commit.

This is fine with me, but do I understand correctly that the PPC
doesn't have a way to return the data address that triggered the
watchpoint?  If so, how do things work on a PPC when GDB calls
target_stopped_data_address?  What am I missing?

Also, please add an entry in NEWS about this.

Last, but not least, thanks for working on this!


  reply	other threads:[~2005-08-17 18:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17 18:30 Manoj Iyer
2005-08-17 18:46 ` Eli Zaretskii [this message]
2005-08-17 23:03 ` Mark Kettenis
2005-08-19  0:53   ` [RFC/RFA] Target vectors for native Linux targets Ulrich Weigand
2005-08-21 10:48     ` Mark Kettenis
2005-08-21 15:21       ` Ulrich Weigand
2005-08-21 15:53         ` Mark Kettenis
2005-09-04 15:48           ` Daniel Jacobowitz
2005-09-04 22:48     ` Daniel Jacobowitz
2005-09-05 17:32       ` Ulrich Weigand
2005-09-10 18:13         ` Daniel Jacobowitz
2005-09-11 22:02           ` [committed] s390 watchpoints (Re: [RFC/RFA] Target vectors for native Linux targets) Ulrich Weigand
2005-09-11 23:09             ` Daniel Jacobowitz
2005-09-18  1:20 ` [RFC] GDB patches for hw watchpoints 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=u8xz02z7k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=manjo@austin.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