Re: MI3 and async notifications
Jonah Graham <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <CAPmGMvjHsivoDCs2Kx4SFxzVFt2s1HqM48hJz2F0bqsQHNrCWw@mail.gmail.com> |
On Fri, 5 Jul 2019 at 16:00, Pedro Alves <[email protected]> wrote: > On 6/11/19 2:37 PM, Jonah Graham wrote: > > On Tue, 11 Jun 2019 at 04:50, Jan Vrany <[email protected]> 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. > To be clear, "CDT will use the mi-always-notify" meant that CDT would make use of the option to turn the always notify *off*. In other words, I wanted GDB to provide it as an option and not have it always on. Jonah