This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2] Fix several "set remote foo-packet on/off" commands.
- From: Pedro Alves <palves at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org, Yao Qi <yao at codesourcery dot com>
- Date: Tue, 29 Apr 2014 14:06:57 +0100
- Subject: Re: [PATCH v2] Fix several "set remote foo-packet on/off" commands.
- Authentication-results: sourceware.org; auth=none
- References: <1396307414-2053-1-git-send-email-palves at redhat dot com> <533A7E83 dot 4070200 at codesourcery dot com> <533AABE1 dot 8040101 at redhat dot com> <533AB01E dot 4060003 at redhat dot com> <20140428191608 dot GA9089 at adacore dot com> <535EF9DC dot 4050706 at redhat dot com> <20140429125351 dot GB4420 at adacore dot com>
On 04/29/2014 01:53 PM, Joel Brobecker wrote:
> Hi Pedro,
>
>> Bummer, sorry for the trouble.
>
> No problem at all!
>
>> I think the design is sound. See more info in the patch below.
>>
>> I'd be fine with either:
>>
>> - restoring things to how they've "always" been immediately.
>> That is, push the patch below. We can then incrementally add the
>> missing associated commands, along with corresponding manual and
>> possibly testsuite changes/additions, as a non-priority task.
>>
>> - or, adding all the missing commands now, and add an assertion just
>> like in the patch below, but with no exception list, of course.
>> (but TBC, I can't offer to work on that myself now.)
>
> Either approach would be fine with me too. I could even see a two-step
> approach where we apply your first patch as a stop-gap, and then
> implement everything as a setting (I think having the setting for
> every packet could prove useful to interact with difficult remote
> stubs).
Alright, so I just went ahead and pushed the patch in.
Thanks,
--
Pedro Alves