From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tdevries@suse.de>
Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28])
 by sourceware.org (Postfix) with ESMTPS id E5FA03858402
 for <gdb-patches@sourceware.org>; Thu, 26 Aug 2021 12:46:33 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E5FA03858402
Received: from imap1.suse-dmz.suse.de (imap1.suse-dmz.suse.de [192.168.254.73])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512)
 (No client certificate requested)
 by smtp-out1.suse.de (Postfix) with ESMTPS id 46FD0222EE;
 Thu, 26 Aug 2021 12:46:09 +0000 (UTC)
Received: from imap1.suse-dmz.suse.de (imap1.suse-dmz.suse.de [192.168.254.73])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512)
 (No client certificate requested)
 by imap1.suse-dmz.suse.de (Postfix) with ESMTPS id 2E07D1364E;
 Thu, 26 Aug 2021 12:46:09 +0000 (UTC)
Received: from dovecot-director2.suse.de ([192.168.254.65])
 by imap1.suse-dmz.suse.de with ESMTPSA id hsJCChGNJ2GuSQAAGKfGzw
 (envelope-from <tdevries@suse.de>); Thu, 26 Aug 2021 12:46:09 +0000
Subject: Re: [RFC][gdb/doc] Document non-stop attach behaviour
From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>
References: <20210607132127.GA10588@delia.home>
 <413e84be-8827-53fb-cd6f-e2ecc66a4af2@polymtl.ca>
 <5a80535d-f7ae-4707-4df5-5efff08e389d@suse.de>
Message-ID: <c39d61f5-7fd8-3215-0747-b06c26e1ebd5@suse.de>
Date: Thu, 26 Aug 2021 14:46:08 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <5a80535d-f7ae-4707-4df5-5efff08e389d@suse.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, SPF_HELO_NONE,
 SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: gdb-patches@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-patches mailing list <gdb-patches.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-patches>,
 <mailto:gdb-patches-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Aug 2021 12:46:45 -0000

On 8/26/21 12:08 PM, Tom de Vries wrote:
> On 8/26/21 4:55 AM, Simon Marchi wrote:
>>
>> I think the behavior could be a bit more user friendly, we could wait
>> for all the attached program's threads to have reported their stop
>> before showing the prompt.  Same with the interrupt (with and without
>> "-a") command, we know which threads we expect to become stopped, we
>> could wait for them to be stopped before giving back the prompt.  That
>> would make it easier for scripts: when the attach / interrupt command
>> returns, you know the attached / interrupted threads are stopped and can
>> be inspected.
> 
> Ack, I can file a PR for that.
> 

Filed PR https://sourceware.org/bugzilla/show_bug.cgi?id=28270.

Thanks,
- Tom