From: Hui Zhu <teawater@gmail.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add command resetbpnum for reset $bpnum
Date: Wed, 21 Sep 2011 06:11:00 -0000 [thread overview]
Message-ID: <CANFwon0BR35u0O+0cUdQA=GF-8B3w-vnFCcY3gVACbcBNJg3Lw@mail.gmail.com> (raw)
In-Reply-To: <m3zki0e4y1.fsf@redhat.com>
Sorry guys.
After a long think about this patch.
I think most issues(they are around python script) that I meet can be
handle by get the last breakpoint id from $bpnum.
So I think I will give up this patch.
But if I meet a issue that only can handle by reset $bpnum, I will post it.
Thanks for your help.
Best,
Hui
On Tue, Sep 20, 2011 at 02:56, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> Stan Shebs <stanshebs@earthlink.net> writes:
>
>> 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.
>
> I second that. I read the patch and couldn't come up with a scenario
> where the user would want to use this `reset' feature. Hui, can you
> explain a bit more why you thought this would be a good idea? I was not
> convinced by your example.
>
prev parent reply other threads:[~2011-09-21 3:55 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
2011-09-19 19:02 ` Sergio Durigan Junior
2011-09-21 6:11 ` Hui Zhu [this message]
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='CANFwon0BR35u0O+0cUdQA=GF-8B3w-vnFCcY3gVACbcBNJg3Lw@mail.gmail.com' \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=stanshebs@earthlink.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