From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>
Subject: Re: [RFA] info (break|watch|trace), use get_number_or_range
Date: Sat, 19 Feb 2011 12:15:00 -0000 [thread overview]
Message-ID: <201102191036.59432.pedro@codesourcery.com> (raw)
In-Reply-To: <4D5F286B.3060207@vmware.com>
On Saturday 19 February 2011 02:18:19, Michael Snyder wrote:
> I've always thought that info break should accept a list and/or a range.
>
> Since this is an enhancement, I'll wait for review. OK?
>
> Eli, I'll wait on the docs change until we agree what it should look like.
This will break printing internal breakpoints, which are
negative.
--
Pedro Alves
next prev parent reply other threads:[~2011-02-19 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 8:21 Michael Snyder
2011-02-19 12:15 ` Pedro Alves [this message]
2011-02-19 19:12 msnyder
2011-02-20 21:34 ` Pedro Alves
2011-02-21 20:05 ` Michael Snyder
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=201102191036.59432.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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