This is the mail archive of the
mailing list for the GDB project.
Re: Some questions about gdb's remote protocol and reverse debugging
- From: Daniel Jacobowitz <drow at false dot org>
- To: Michael Snyder <msnyder at vmware dot com>
- Cc: Julian Smith <jsmith at undo-software dot com>, "gdb at sources dot redhat dot com" <gdb at sources dot redhat dot com>
- Date: Tue, 11 Aug 2009 19:37:41 -0400
- Subject: Re: Some questions about gdb's remote protocol and reverse debugging
- References: <email@example.com> <4A81FD36.firstname.lastname@example.org>
On Tue, Aug 11, 2009 at 04:22:30PM -0700, Michael Snyder wrote:
> >Is there any way to tell gdb to try to use hardware breakpoints (with
> >the 'Z1' and 'z1' commands) before resorting to 'M' and 'm' ? [In the
> >environment i'm working in, UndoDB, hardware breakpoints are more
> >convenient because they don't require any patching up of %pc, and
> >poking breakpoints directly into memory is not supported.]
> Not as such, no. You use a different syntax to set a hardware
> breakpoint. The command is "hbreak" instead of "break". You
> should at least be able to try stuff out with that.
Or, just make your stub treat Z0 as a hardware breakpoint?