Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: Remote watchpoint support for FRV
Date: Sun, 14 Oct 2007 20:13:00 -0000	[thread overview]
Message-ID: <200710141955.l9EJtCNc031302@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20071005135640.GA17031@caradoc.them.org> from "Daniel Jacobowitz" at Oct 05, 2007 09:56:40 AM

Daniel Jacobowitz wrote:
> On Fri, Oct 05, 2007 at 03:47:53PM +0200, Ulrich Weigand wrote:
> > Hello,
> > 
> > the tm-frv.h header file overrides a number of watchpoint related
> > target macros, in particular:
> > 
> > #define STOPPED_BY_WATCHPOINT(W) \
> >    ((W).kind == TARGET_WAITKIND_STOPPED \
> >    && (W).value.sig == TARGET_SIGNAL_TRAP \
> >    && frv_have_stopped_data_address())
> 
> Kevin, you were the last person to work on the FRV target (far as I
> can tell); do you know anything about this?

Any updates on this?  I've had another look at this, and it appears
to me that this wasn't actually functional in mainline GDB anyway:
Up until your recent breakpoint.c change, watchpoints were active 
only if either HAVE_STEPPABLE_WATCHPOINT, HAVE_NONSTEPPABLE_WATCHPOINT,
or HAVE_CONTINUABLE_WATIPOINT were defined.

In this particular case, the tm file doesn't define any of these (the
#define HAVE_STEPPABLE_WATCHPOINT is commented out), an nm file doesn't
apply, the remote target does not define to_have_continuable_watchpoint,
and frv-tdep does not use set_gdbarch_nonsteppable_watchpoint.

Thus it would appear that the STOPPED_BY_WATCHPOINT and 
target_stopped_data_address macros defined in the tm-frv.h header
file aren't actually ever called.  (Since the recent watchpoint change,
they *are* active, but probably not correctly as common code now assumes
continuable watchpoint behaviour).

Note that the HAVE_STEPPABLE_WATCHPOINT macro is commented out since the
very first version of tm-frv.h checked into the GDB CVS, so I'm not sure
what to think of that ...  Did this ever work?

If it actually didn't ever work, I'd say we should just remove the tm
file now; if somebody wants to get remote watchpoint support on frv
working, they can (and should) use the existing mechanism.

> Ulrich, there's a third option, but I don't know if it's practical.
> Can we somehow specialize the remote target based on the architecture?
> It's not the first time I've thought it would be useful.  But we
> already have the target adjusting the architecture and adding
> something in the other direction might be awkward.

I agree this would probably be a bit awkward ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2007-10-14 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 13:48 Ulrich Weigand
2007-10-05 13:56 ` Daniel Jacobowitz
2007-10-14 20:13   ` Ulrich Weigand [this message]
2007-10-24 19:34     ` Daniel Jacobowitz
2007-10-24 21:06       ` [commit] " 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=200710141955.l9EJtCNc031302@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.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