From: "J.T. Conklin" <jtc@RedBackNetworks.com>
To: gdb@cygnus.com
Subject: Re: breakpoint extension for remote protocol
Date: Fri, 11 Dec 1998 14:30:00 -0000 [thread overview]
Message-ID: <199812112229.OAA25621@jtc.redbacknetworks.com> (raw)
In-Reply-To: <199812111958.LAA25479@jtc.redbacknetworks.com>
> Although I noticed the parallelism of the existing commands g/G, m/M,
> and I recently proposed p to compliment P; I used B/D instead of b/B
> because inserting and removing breakpoints don't have quite the same
> type of symmetry as reading and writing memory or registers. A read
> command doesn't change the state of the target, while removing a
> breakpoint certainly does.
FYI,
While re-reading the protocol spec described in remote.c, I discovered
the existing 'D' (detach) command, so I'm now using 'b' instead of 'D'
for removing break/watchpoints.
> One issue with 'b' is that it's used in the sparc* stubs to set the
> baud rate of the connection. That code has been #ifdef'd out with
> the comment "Disabled until we can unscrew this properly", so we may
> be able to simply junk that.
--jtc
J.T. Conklin
RedBack Networks
next prev parent reply other threads:[~1998-12-11 14:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199812041858.KAA25185.cygnus.gdb@jtc.redbacknetworks.com>
1998-12-10 19:27 ` Andrew Cagney
1998-12-10 21:46 ` Stu Grossman
1998-12-11 11:59 ` J.T. Conklin
1998-12-11 14:30 ` J.T. Conklin [this message]
1998-12-11 11:24 ` J.T. Conklin
[not found] ` <13936.45476.191551.329690.cygnus.gdb@babylon-5.cygnus.com>
1999-04-01 0:00 ` Andrew Cagney
1999-04-01 0:00 ` J.T. Conklin
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` Jim Blandy
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` GDB: one version for all targets Brendan Simon
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` breakpoint extension for remote protocol J.T. Conklin
[not found] <199901050119.RAA19672.cygnus.gdb@jtc.redbacknetworks.com>
1999-04-01 0:00 ` Andrew Cagney
1998-12-04 10:59 J.T. Conklin
1998-12-23 13:07 ` Greg McGary
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=199812112229.OAA25621@jtc.redbacknetworks.com \
--to=jtc@redbacknetworks.com \
--cc=gdb@cygnus.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