From: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
To: gdb@sourceware.org
Subject: Modifications on gdbserver
Date: Tue, 29 Sep 2009 19:40:00 -0000 [thread overview]
Message-ID: <200909291640.14995.sergiodj@linux.vnet.ibm.com> (raw)
Hello guys,
I'm extending gdbserver in order to accept new types of hardware
breakpoints/watchpoints, and trying to figure out how to do this in the best
way. Specifically, right now I'm implementing the support for hardware ranged
breakpoints (one will be able to specify an address and a range, and GDB will
stop whenever the inferior executes code within this range), and there are
some ways to do it:
1) I could extend the remote protocol and include one more type of `Z' packet
(`Z5', for example) which would represent this type of hardware breakpoint.
2) I could extend the existing `Z1' (hardware breakpoint) packet in order to
include a "length" (or "range") parameter. This will be different from the
existing "size" parameter, because "size" is currently used the size of the
instruction on the architecture.
What do you think? Considering that there will be more "special" types of
hardware breakpoints/watchpoints, probably I should choose (2) and try to
modify the remote protocol as few as possible. Do you agree? Also, do you
see other option(s) that could be better for this case?
Best regards,
--
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil
next reply other threads:[~2009-09-29 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 19:40 Sérgio Durigan Júnior [this message]
2009-09-29 19:48 ` Daniel Jacobowitz
2009-09-29 20:09 ` Sérgio Durigan Júnior
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=200909291640.14995.sergiodj@linux.vnet.ibm.com \
--to=sergiodj@linux.vnet.ibm.com \
--cc=gdb@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