From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 93985 invoked by alias); 5 Jul 2019 21:58:53 -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 93977 invoked by uid 89); 5 Jul 2019 21:58:53 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=H*f:sk:388ffb3, H*i:sk:388ffb3, H*c:alternative X-HELO: pb-smtp1.pobox.com Received: from pb-smtp1.pobox.com (HELO pb-smtp1.pobox.com) (64.147.108.70) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 05 Jul 2019 21:58:52 +0000 Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 8F3F3168DC5 for ; Fri, 5 Jul 2019 17:58:47 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; s=sasl; bh=cNPLUubyCKi4sHalhikMcEDShT0=; b=vOa53k vyPNtvZQSqMPhjgssTz6SCX1C4noxE/wy4ugSs+UEkjOVh01voV/GLUaDjcyu/lo XMl/srrYrojSUw8bFh0g+oLvH+4jZ9o8eMwHqCIAK9/FjzeEZdRo7TCG0IVt6N1S imVpCPqZ3a6T9mN6H6Xukzk+2x8HDuFDAsH48= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 86D7B168DC2 for ; Fri, 5 Jul 2019 17:58:46 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=kichwacoders.com; h=mime-version:references:in-reply-to:from:date:message-id:subject:to:cc:content-type; s=mesmtp; bh=zLd4X5PGTCs+0/hlQTDQYKYdWz5HCTXc6KBfomNXC0A=; b=ZJ9twU6EAJRVGeK7VeElJEysPQhTs3xaO4mTQZDlQAFBFzU6J137FA/wTNOeP7jOmYt9ja2L6sHBymCfr+hcHqt96gkOr9nasvSdCVqg7FmumcoUcfyTxwuS6dIj2SHHJRVl/2R1UKcFBs/I67A3jbP/06ZAD/v4qCzZ7iCCTrs= Received: from mail-qt1-f169.google.com (unknown [209.85.160.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id F0239168DC0 for ; Fri, 5 Jul 2019 17:58:45 -0400 (EDT) Received: by mail-qt1-f169.google.com with SMTP id h24so12621572qto.0 for ; Fri, 05 Jul 2019 14:58:45 -0700 (PDT) MIME-Version: 1.0 References: <70fdd9107d9bb3cee0a1a342aedc05bf3c8e9bae.camel@fit.cvut.cz> <6d00108e3693957c4d2e648bae64cb9f4fce63bd.camel@fit.cvut.cz> <388ffb33-bb44-b997-fcda-b9585d51e360@redhat.com> In-Reply-To: <388ffb33-bb44-b997-fcda-b9585d51e360@redhat.com> From: Jonah Graham Date: Fri, 05 Jul 2019 21:58:00 -0000 Message-ID: Subject: Re: MI3 and async notifications To: Pedro Alves Cc: Jan Vrany , "gdb@sourceware.org" X-Pobox-Relay-ID: 0FB1E496-9F70-11E9-BE78-46F8B7964D18-18936988!pb-smtp1.pobox.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-07/txt/msg00002.txt.bz2 On Fri, 5 Jul 2019 at 16:00, Pedro Alves wrote: > 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. > 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