This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: MI3 and async notifications
- From: Pedro Alves <palves at redhat dot com>
- To: Jonah Graham <jonah at kichwacoders dot com>, Jan Vrany <jan dot vrany at fit dot cvut dot cz>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Fri, 5 Jul 2019 21:00:40 +0100
- Subject: Re: MI3 and async notifications
- References: <70fdd9107d9bb3cee0a1a342aedc05bf3c8e9bae.camel@fit.cvut.cz> <CAPmGMvjDKHQPH7y3aYC-v3C75D8rO42FhWf_MsFK7p49aGZQpQ@mail.gmail.com> <6d00108e3693957c4d2e648bae64cb9f4fce63bd.camel@fit.cvut.cz> <CAPmGMvhcGDD=WbY06JTwESugwifBeR_p2eBnRyToR-FW9VKoYw@mail.gmail.com>
On 6/11/19 2:37 PM, Jonah Graham wrote:
> On Tue, 11 Jun 2019 at 04:50, Jan Vrany <jan.vrany@fit.cvut.cz> wrote:
>
>> As you can see, you get the notification *before* ^done response. Does
>> that answer
>> your questions?
>>
>>
> Yes that does. I think CDT will use the mi-always-notify option.
Funny. ISTR that the breakpoint notification suppressing was
originally done for CDT and reading/hearing Vladimir argue for
it. :-D Though I can't find any arguing about that aspect
around the original patch now:
https://sourceware.org/ml/gdb-patches/2011-04/msg00471.html
Vladimir said "As other MI notifications", but I checked out
the tree for that commit (8d3788bd590a), and I couldn't find
any other suppression that existed back then.
Thanks,
Pedro Alves