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: Tue, 01 Jul 2003 14:04:00 -0000 [thread overview]
Message-ID: <078301c33fd9$a8f6de30$1400a8c0@astral> (raw)
In-Reply-To: <3EF5C78D.30803@redhat.com>
----- 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
next prev parent reply other threads:[~2003-07-01 14:04 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.
2003-06-22 15:34 ` Andrew Cagney
2003-07-01 14:04 ` John S. Yates, Jr. [this message]
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='078301c33fd9$a8f6de30$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).