This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Add command resetbpnum for reset $bpnum


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.
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]