* supporting hw break/watch for embedded ppc
@ 2003-06-03 20:34 John S. Yates, Jr.
2003-06-08 19:17 ` Andrew Cagney
0 siblings, 1 reply; 7+ messages in thread
From: John S. Yates, Jr. @ 2003-06-03 20:34 UTC (permalink / raw)
To: gdb
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.
So where do I go to enable ppc hw breaks/watches?
/john
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: supporting hw break/watch for embedded ppc
2003-06-03 20:34 supporting hw break/watch for embedded ppc John S. Yates, Jr.
@ 2003-06-08 19:17 ` Andrew Cagney
2003-06-09 15:07 ` John S. Yates, Jr.
0 siblings, 1 reply; 7+ messages in thread
From: Andrew Cagney @ 2003-06-08 19:17 UTC (permalink / raw)
To: John S. Yates, Jr.; +Cc: gdb
> 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.
Andrew
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: supporting hw break/watch for embedded ppc
2003-06-08 19:17 ` Andrew Cagney
@ 2003-06-09 15:07 ` John S. Yates, Jr.
2003-06-22 15:34 ` Andrew Cagney
0 siblings, 1 reply; 7+ messages in thread
From: John S. Yates, Jr. @ 2003-06-09 15:07 UTC (permalink / raw)
To: Andrew Cagney; +Cc: gdb
> > 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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: supporting hw break/watch for embedded ppc
2003-06-09 15:07 ` John S. Yates, Jr.
@ 2003-06-22 15:34 ` Andrew Cagney
2003-07-01 14:04 ` John S. Yates, Jr.
0 siblings, 1 reply; 7+ messages in thread
From: Andrew Cagney @ 2003-06-22 15:34 UTC (permalink / raw)
To: John S. Yates, Jr.; +Cc: gdb
>> > 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;
Have you tried:
(gdb) help set remote hardware-breakpoint-limit
Set the maximum number of target hardware breakpoints.
Specify a negative limit for unlimited.
> 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?
There is a discussion and thread about improving the way GDB queries the
target for its level of watchpoint support. It involves some
re-aranging of the breakpoints though (look for a thread between my
self and Eli).
I've been to busy fixing up frames.
Andrew
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: supporting hw break/watch for embedded ppc
2003-06-22 15:34 ` Andrew Cagney
@ 2003-07-01 14:04 ` John S. Yates, Jr.
2003-07-01 14:16 ` Andrew Cagney
0 siblings, 1 reply; 7+ messages in thread
From: John S. Yates, Jr. @ 2003-07-01 14:04 UTC (permalink / raw)
To: Andrew Cagney; +Cc: gdb
----- Original Message -----
From: "Andrew Cagney" <ac131313@redhat.com>
Subject: Re: supporting hw break/watch for embedded ppc
> Have you tried:
>
> (gdb) help set remote hardware-breakpoint-limit
> Set the maximum number of target hardware breakpoints.
> Specify a negative limit for unlimited.
No I had not. Now that you point it out I do
see the command documented in my most recent
gdb.pdf based on TexInfo 20003-02-03.16. This
does not seem to reflect the 5.3 sources from
which I am working. In those the command does
not exit. (remote_hardware_breakpoint_limit
and remote_hardware_watchpoint_limit do exist
as variables within remote.c but there seems to
be no code to update them.)
/john
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: supporting hw break/watch for embedded ppc
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.
0 siblings, 1 reply; 7+ messages in thread
From: Andrew Cagney @ 2003-07-01 14:16 UTC (permalink / raw)
To: John S. Yates, Jr.; +Cc: gdb
> ----- Original Message -----
> From: "Andrew Cagney" <ac131313@redhat.com>
> Subject: Re: supporting hw break/watch for embedded ppc
>
>
>
>> Have you tried:
>>
>> (gdb) help set remote hardware-breakpoint-limit
>> Set the maximum number of target hardware breakpoints.
>> Specify a negative limit for unlimited.
>
>
> No I had not. Now that you point it out I do
> see the command documented in my most recent
> gdb.pdf based on TexInfo 20003-02-03.16. This
> does not seem to reflect the 5.3 sources from
> which I am working.
Sounds like a snap of the current doco, does the front page read ``for
GDB Version YYYYMMDD''?
Andrew
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: supporting hw break/watch for embedded ppc
2003-07-01 14:16 ` Andrew Cagney
@ 2003-07-01 14:44 ` John S. Yates, Jr.
0 siblings, 0 replies; 7+ messages in thread
From: John S. Yates, Jr. @ 2003-07-01 14:44 UTC (permalink / raw)
To: Andrew Cagney; +Cc: gdb
----- Original Message -----
From: "Andrew Cagney" <ac131313@redhat.com>
Subject: Re: supporting hw break/watch for embedded ppc
> Sounds like a snap of the current doco, does the front page read ``for
> GDB Version YYYYMMDD''?
"Ninth Edition, for gdb version 20030404"
/john
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2003-07-01 14:44 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-06-03 20:34 supporting hw break/watch for embedded ppc John S. Yates, Jr.
2003-06-08 19:17 ` Andrew Cagney
2003-06-09 15:07 ` John S. Yates, Jr.
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.
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).