This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/2] Support the new PPC476 processor
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: S?rgio Durigan J?nior <sergiodj at linux dot vnet dot ibm dot com>, gdb-patches at sourceware dot org, bauerman at br dot ibm dot com, luisgpm at linux dot vnet dot ibm dot com, tyrlik at us dot ibm dot com
- Date: Sun, 20 Dec 2009 16:33:24 +0400
- Subject: Re: [PATCH 0/2] Support the new PPC476 processor
- References: <200912161847.17162.sergiodj@linux.vnet.ibm.com> <83y6l060qp.fsf@gnu.org>
> > - Usage example: watch-range &i,&k / awatch-range 0xbffff8e8,0xbffff8f8 /
> > rwatch-range 0xbffff8e8,+8
>
> Why is there a need for a separate GDB command? What are the
> use-cases where the user would want to watch a region that is spanned
> by more than one (albeit large) variable? If such use-cases are
> infrequent enough or obscure, then we could simply use the normal
> watch commands, and support any corner use-cases with something like
>
> watch *0xbffff8e8@8
FWIW, I actually prefer the seperate command over your suggestion.
The use of the @8 seems logical, but '@' is little known and the
new command seems more explicit about the actual range being watched.
--
Joel