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 dap/31306] [gdb/dap] segfault in new_threadstate during gdb.dap/eof.exp
Date: Mon, 05 Feb 2024 16:24:13 +0000 [thread overview]
Message-ID: <bug-31306-4717-0yqxCMnKA0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31306-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31306
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #4)
> (In reply to Tom de Vries from comment #2)
> > Could be a dup or PR31172. The tentative patch posted there makes this PR
> > less likely to occur, but it still does. Which almost looks like a runnable
> > was posted while quitting.
>
> Could it be the runnable that is posted to cause the quit?
> io.py does:
>
> if obj is None:
> # This is an exit request. The stream is already
> # flushed, so all that's left to do is request an
> # exit.
> send_gdb("quit")
> break
Thanks for the hint. I think there's a race between:
- a SIGHUP, and
- send_gdb("quit")
So, with clean sources, we have:
- gdb receives a SIGHUP, calls quit_force
- at that point, runnables contains quit in a python wrapper
- python is finalized, so the python global interpreter lock is
no longer available
- runnables is destroyed, which trigger the destruction of a gdbpy_event, which
requires the python global interpreter lock
- segfault when trying to acquire the no longer availabe python global
interpreter
lock
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-05 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 6:49 [Bug dap/31306] New: " vries at gcc dot gnu.org
2024-01-29 10:00 ` [Bug dap/31306] " vries at gcc dot gnu.org
2024-01-29 10:56 ` vries at gcc dot gnu.org
2024-01-29 11:53 ` vries at gcc dot gnu.org
2024-01-29 11:54 ` vries at gcc dot gnu.org
2024-01-29 17:20 ` tromey at sourceware dot org
2024-01-29 21:18 ` vries at gcc dot gnu.org
2024-02-05 16:24 ` vries at gcc dot gnu.org [this message]
2024-02-07 9:03 ` vries at gcc dot gnu.org
2024-02-12 18:58 ` tromey at sourceware dot org
2024-02-14 17:24 ` cvs-commit at gcc dot gnu.org
2024-02-14 17:25 ` 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-31306-4717-0yqxCMnKA0@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).