Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: eliz@gnu.org
Cc: woodzltc@cn.ibm.com (Wu Zhou), gdb-patches@sourceware.org
Subject: Re: [ppc-linux-nat]: set access flag for h/w watchpoint even if it      is  only read or write
Date: Sat, 08 Jul 2006 19:36:00 -0000	[thread overview]
Message-ID: <200607081936.k68Jae7v010393@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <uveq9pi4j.fsf@gnu.org> from "Eli Zaretskii" at Jul 07, 2006 06:08:44 PM

Eli Zaretskii wrote:
> > Date: Fri, 7 Jul 2006 09:17:54 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Wu Zhou <woodzltc@cn.ibm.com>, gdb-patches@sourceware.org
> > 
> > > Daniel, could you please point me to Ulrich's change, either in
> > > ChangeLogs or in the sources?  I cannot find it forf some reason.
> > 
> > I must be mistaken; our S/390 support doesn't have any read watchpoints
> > (I don't know if the architecture does or not).  In fact I can't find
> > any architecture that does this.  But I immediately recognized
> > the description of the problem... so it must have happened somewhere.
> 
> You are not dreaming, because I remember that as well.  Perhaps Ulrich
> just suggested a change, but it wasn't accepted eventually.

I'm not sure which conversation you're referring to.  In any case, S/390
does not support read watchpoints at all, neither by themselves nor in
combination with a write watchpoint.  The only type of hardware watchpoint
it supports is the pure write watchpoint.

I do recall some discussion about watchpoints on S/390, but that had to
do with the fact that on our platform, the hardware does not identify
the data address that triggered the watchpoint, and there were some
changes to GDB common code that implicitly assumed that the target 
should be able to do that ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  Linux on zSeries Development
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2006-07-08 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07  4:35 Wu Zhou
2006-07-07 10:04 ` Eli Zaretskii
2006-07-07 13:18   ` Daniel Jacobowitz
2006-07-07 15:08     ` Eli Zaretskii
2006-07-08 19:36       ` Ulrich Weigand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-09 15:40 Wu Zhou
2006-07-06 13:20 ` Daniel Jacobowitz
2006-07-06 20:59   ` Eli Zaretskii
2006-07-06 21:37     ` 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=200607081936.k68Jae7v010393@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=woodzltc@cn.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