public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/27908] FAIL: gdb.base/run-attach-while-running.exp: threaded=1: run-or-attach=attach: non-stop=on: test: attach to process (timeout)
Date: Mon, 07 Jun 2021 13:29:41 +0000 [thread overview]
Message-ID: <bug-27908-4717-ladt2Bx2tc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27908-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27908
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|gdb |testsuite
--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #9)
> (In reply to Tom de Vries from comment #8)
> > Looks like a regression, passed at gdb-10-branch branchpoint.
>
> Hmm, that bisects to:
> ...
> commit 2ab76a181f3db93f051aaae66d65ff2733884d96
> Author: Pedro Alves <pedro@palves.net>
> Date: Wed Dec 23 00:34:54 2020 +0000
>
> Fix attaching in non-stop mode (PR gdb/27055)
> ...
>
> Looking in the test-case attach-non-stop.exp, it seems that the "thread
> stopped" message is expected.
>
> This makes no sense to me. In non-stop mode, I'm expecting only one thread
> to stop. Why do we expect all threads to stop? Isn't that all-stop mode
> behaviour?
After rereading the documentation once more, I guess not. The non-stop mode
only affects moments when "a thread stops to report a debugging event". So, I
guess attaching is not a debugging event? I was not able to find a definition.
Anyway, I've submitted an RFC patch (
https://sourceware.org/pipermail/gdb-patches/2021-June/179615.html ) that
documents the behaviour of attach in non-stop mode, hopefully that will make
things a bit easier to understand.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-07 13:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 8:44 [Bug gdb/27908] New: " vries at gcc dot gnu.org
2021-05-25 8:46 ` [Bug gdb/27908] " vries at gcc dot gnu.org
2021-05-25 8:47 ` vries at gcc dot gnu.org
2021-05-25 9:13 ` vries at gcc dot gnu.org
2021-05-25 9:25 ` vries at gcc dot gnu.org
2021-05-25 9:25 ` vries at gcc dot gnu.org
2021-05-25 10:00 ` vries at gcc dot gnu.org
2021-05-25 10:06 ` vries at gcc dot gnu.org
2021-05-25 10:18 ` vries at gcc dot gnu.org
2021-05-25 11:37 ` vries at gcc dot gnu.org
2021-05-25 12:35 ` vries at gcc dot gnu.org
2021-06-07 13:29 ` vries at gcc dot gnu.org [this message]
2021-06-07 13:46 ` [Bug testsuite/27908] " cvs-commit at gcc dot gnu.org
2021-06-07 13:47 ` vries at gcc dot gnu.org
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=bug-27908-4717-ladt2Bx2tc@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).