From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add command resetbpnum for reset $bpnum
Date: Mon, 19 Sep 2011 17:26:00 -0000 [thread overview]
Message-ID: <4E777733.8010107@earthlink.net> (raw)
In-Reply-To: <CANFwon0CgAn4UHi6d=CHSB69mRqYCFx0Xbfay7ZHD7ML1ur8iQ@mail.gmail.com>
On 9/18/11 9:16 AM, Hui Zhu wrote:
> Hi,
>
> I found we never set the breakpoint number back in GDB. And sometime,
> I fount that user need reset $bpnum to the current last number.
> So I make a patch add command resetbpnum for reset $bpnum to the last
> number of the current breakpoints.
>
>
I tend to think this would not be a good idea. Although I don't know
that we have a formal requirement that breakpoint numbers are all unique
within a session, it's certainly a common assumption that we rely on
when looking at user transcripts, testsuite runs, etc.
So before breaking before one of the longest-standing UI design
decisions in GDB, it seems like we ought to get a little more
understanding of why a user might want to reset breakpoint numbering.
Stan
stan@codesourcery.com
next prev parent reply other threads:[~2011-09-19 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 3:50 Hui Zhu
2011-09-19 17:26 ` Stan Shebs [this message]
2011-09-19 19:02 ` Sergio Durigan Junior
2011-09-21 6:11 ` Hui Zhu
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=4E777733.8010107@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb-patches@sourceware.org \
/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