From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>
Subject: Re: [RFC][gdb/doc] Document non-stop attach behaviour
Date: Thu, 26 Aug 2021 14:46:08 +0200 [thread overview]
Message-ID: <c39d61f5-7fd8-3215-0747-b06c26e1ebd5@suse.de> (raw)
In-Reply-To: <5a80535d-f7ae-4707-4df5-5efff08e389d@suse.de>
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
prev parent reply other threads:[~2021-08-26 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 13:21 Tom de Vries
2021-08-24 11:10 ` [PING][RFC][gdb/doc] " Tom de Vries via Gdb-patches
2021-08-26 2:55 ` [RFC][gdb/doc] " Simon Marchi via Gdb-patches
2021-08-26 10:08 ` Tom de Vries via Gdb-patches
2021-08-26 12:46 ` Tom de Vries via Gdb-patches [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c39d61f5-7fd8-3215-0747-b06c26e1ebd5@suse.de \
--to=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox