From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: S?rgio Durigan J?nior <sergiodj@linux.vnet.ibm.com>,
gdb-patches@sourceware.org, bauerman@br.ibm.com,
luisgpm@linux.vnet.ibm.com, tyrlik@us.ibm.com
Subject: Re: [PATCH 0/2] Support the new PPC476 processor
Date: Sun, 20 Dec 2009 12:33:00 -0000 [thread overview]
Message-ID: <20091220123324.GG2788@adacore.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2009-12-20 12:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 20:48 Sérgio Durigan Júnior
2009-12-17 4:42 ` Joel Brobecker
2009-12-17 14:19 ` Thiago Jung Bauermann
2009-12-17 16:15 ` Sérgio Durigan Júnior
2009-12-18 10:19 ` Eli Zaretskii
2009-12-20 12:33 ` Joel Brobecker [this message]
2009-12-30 3:13 ` Thiago Jung Bauermann
2009-12-30 20:43 ` Eli Zaretskii
2009-12-30 22:15 ` Daniel Jacobowitz
2009-12-31 4:05 ` Eli Zaretskii
2009-12-31 16:28 ` Daniel Jacobowitz
2009-12-31 16:50 ` Pedro Alves
2009-12-20 13:16 ` Joel Brobecker
2009-12-20 15:09 ` Sérgio Durigan Júnior
2009-12-20 18:24 ` Joel Brobecker
2009-12-21 12:54 ` Thiago Jung Bauermann
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=20091220123324.GG2788@adacore.com \
--to=brobecker@adacore.com \
--cc=bauerman@br.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.com \
--cc=sergiodj@linux.vnet.ibm.com \
--cc=tyrlik@us.ibm.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