This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] info (break|watch|trace), use get_number_or_range
- From: Pedro Alves <pedro at codesourcery dot com>
- To: msnyder at sonic dot net
- Cc: gdb-patches at sourceware dot org
- Date: Sun, 20 Feb 2011 21:29:11 +0000
- Subject: Re: [RFA] info (break|watch|trace), use get_number_or_range
- References: <9c90ed265767e17ab56f1f865d10999d.squirrel@webmail.sonic.net>
On Saturday 19 February 2011 18:01:44, msnyder@sonic.net wrote:
>
> > This will break printing internal breakpoints, which are negative.
>
> AFAIK, "info break" never supported printing internal breakpoints.
> That's what "maint info break" is for.
Sorry, I misread and though you were changing breakpoint_1, which
is the backend for "info break", "maint info break", etc.
Doesn't this patch have the same problem I pointed out with
"info threads 1-100", in that you'll print the header once
for each breakpoint in the range?
--
Pedro Alves