This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: i386 debugging registers
- To: fnasser at cygnus dot com
- Subject: Re: i386 debugging registers
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Mon, 12 Jun 2000 08:46:17 -0400 (EDT)
- CC: kettenis at wins dot uva dot nl, gdb at sourceware dot cygnus dot com, nsd at cygnus dot com, Peter dot Schauer at regent dot e-technik dot tu-muenchen dot de, rjl at sco dot com, cgf at cygnus dot com, jtc at redback dot com, jimb at cygnus dot com
- References: <200006112322.e5BNM6513971@delius.kettenis.local> <3944218C.6FAAA98A@cygnus.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Sun, 11 Jun 2000 23:32:28 +0000
> From: Fernando Nasser <fnasser@cygnus.com>
>
> I can see one situation where one may want to look at or set
> debugger registers: when debugging a debugger's hardware breakpoint
> support.
Yes, definitely. I found myself doing that a lot when I enhanced the
hardware watchpoint/breakpoint support in go32-nat.c (you will see in
the sources an #ifdef'ed away fragment which, if $GDB_SHOW_DR is set
in the environment, causes go32-nat.c to print current values of debug
registers).
> We can add a maintenance command to access that. That is what maintenance
> commands are for.
I agree: a maint command that prints the debug registers would be very
useful.