From: "John S. Yates, Jr." <jyates@netezza.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: "gdb" <gdb@sources.redhat.com>
Subject: Re: supporting hw break/watch for embedded ppc
Date: Mon, 09 Jun 2003 15:07:00 -0000 [thread overview]
Message-ID: <012a01c32e98$ce0beaa0$1400a8c0@astral> (raw)
In-Reply-To: <3EE38BB8.1060904@redhat.com>
> > I have an mpc855 remote stub that implements Z0/z0.
> > This worked entirely as expected. Auto-detection
> > used to attempt Z0, discover it was unsupported,
> > and refrained from ever trying it again. Naively I
> > assumed that the remaining Zt variants would behave
> > similarly. This is not the case.
>
> It should be the case.
>
> > So where do I go to enable ppc hw breaks/watches?
>
> ``set debug remote 1'' to see exactly what the host/target are doing.
Been there. Done that.
The culprit is remote.c/remote_check_watch_resources
which is hardwired via the earlier definitions:
int remote_hw_watchpoint_limit = 0;
int remote_hw_breakpoint_limit = 0;
For now I have added comparisons between chip names
and TARGET_ARCHITECTURE->printable_name along with
corresponding known numbers of resource. It ain't
pretty but it does work.
Am I missing something?
I do not see a parameterized abstraction here that
would operate off the # of hw breakpoint resources,
the # of hw watchpoint resource and an indication
that heterogeneous watch sets are supported (see the
"ot" argument to remote_check_watch_resources).
Nor do I see a way to provide a chip-specific
implementation of to_can_use_hw_breakpoint.
(But then I have zero grasp of how architectural
parameterization works. I just grep and look for
obvious patterns that I can mimic.)
/john
next prev parent reply other threads:[~2003-06-09 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 20:34 John S. Yates, Jr.
2003-06-08 19:17 ` Andrew Cagney
2003-06-09 15:07 ` John S. Yates, Jr. [this message]
2003-06-22 15:34 ` Andrew Cagney
2003-07-01 14:04 ` John S. Yates, Jr.
2003-07-01 14:16 ` Andrew Cagney
2003-07-01 14:44 ` John S. Yates, Jr.
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='012a01c32e98$ce0beaa0$1400a8c0@astral' \
--to=jyates@netezza.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).