From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124644 invoked by alias); 5 Jul 2019 20:00:46 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 124633 invoked by uid 89); 5 Jul 2019 20:00:45 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=cdt, suppressing, CDT X-HELO: mail-wm1-f41.google.com Received: from mail-wm1-f41.google.com (HELO mail-wm1-f41.google.com) (209.85.128.41) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 05 Jul 2019 20:00:44 +0000 Received: by mail-wm1-f41.google.com with SMTP id z23so10759499wma.4 for ; Fri, 05 Jul 2019 13:00:43 -0700 (PDT) Return-Path: Received: from ?IPv6:2001:8a0:f913:f700:4c97:6d52:2cea:997b? ([2001:8a0:f913:f700:4c97:6d52:2cea:997b]) by smtp.gmail.com with ESMTPSA id f17sm3970934wmf.27.2019.07.05.13.00.41 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Fri, 05 Jul 2019 13:00:41 -0700 (PDT) Subject: Re: MI3 and async notifications To: Jonah Graham , Jan Vrany References: <70fdd9107d9bb3cee0a1a342aedc05bf3c8e9bae.camel@fit.cvut.cz> <6d00108e3693957c4d2e648bae64cb9f4fce63bd.camel@fit.cvut.cz> Cc: "gdb@sourceware.org" From: Pedro Alves Message-ID: <388ffb33-bb44-b997-fcda-b9585d51e360@redhat.com> Date: Fri, 05 Jul 2019 20:00:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-07/txt/msg00001.txt.bz2 On 6/11/19 2:37 PM, Jonah Graham wrote: > On Tue, 11 Jun 2019 at 04:50, Jan Vrany 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