From: Pedro Alves <pedro@codesourcery.com>
To: msnyder@sonic.net
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] info (break|watch|trace), use get_number_or_range
Date: Sun, 20 Feb 2011 21:34:00 -0000 [thread overview]
Message-ID: <201102202129.11630.pedro@codesourcery.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2011-02-20 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 19:12 msnyder
2011-02-20 21:34 ` Pedro Alves [this message]
2011-02-21 20:05 ` Michael Snyder
-- strict thread matches above, loose matches on Subject: below --
2011-02-19 8:21 Michael Snyder
2011-02-19 12:15 ` Pedro Alves
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=201102202129.11630.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@sonic.net \
/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