public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "thiago.bauermann at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/31512] gdb.threads/attach-many-short-lived-threads.exp sometimes fails with "process 2689792 is already traced by process 2039527"
Date: Tue, 19 Mar 2024 18:28:31 +0000	[thread overview]
Message-ID: <bug-31512-4717-2CyfoptyZp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31512-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31512

--- Comment #1 from Thiago Jung Bauermann <thiago.bauermann at linaro dot org> ---
In bug #31312 where I first saw this issue, Tom Tromey gave a suggestion on how
to investigate this problem:

> Yeah, what I would suggest is maybe modifying the test case to
> invoke 'strace gdb ..' with some options to log the strace output
> to a file; then examine the file to see if gdb correctly detaches
> from all the threads it attached to.
> 
> That is, I'm wondering if there's some underlying bug that we haven't
> properly recognized -- this would account for the weirdness where
> one failed attach leaves gdb unable to attach in the future.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2024-03-19 18:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 18:17 [Bug threads/31512] New: " thiago.bauermann at linaro dot org
2024-03-19 18:28 ` thiago.bauermann at linaro dot org [this message]
2024-03-19 18:54 ` [Bug threads/31512] " thiago.bauermann at linaro dot 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-31512-4717-2CyfoptyZp@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).