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, 29 Jan 2024 10:00:13 +0000 [thread overview] Message-ID: <bug-31306-4717-B8Nh2DWxCk@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 #1 from Tom de Vries <vries at gcc dot gnu.org> --- Found some related info here: https://docs.python.org/3/c-api/init.html#c.PyGILState_Ensure This fixes it: ... diff --git a/gdb/python/python.c b/gdb/python/python.c index de3a94dfc9a..537db58d8ab 100644 --- a/gdb/python/python.c +++ b/gdb/python/python.c @@ -1048,6 +1048,8 @@ struct gdbpy_event ~gdbpy_event () { + if (_Py_IsFinalizing ()) + return; gdbpy_gil gil; Py_XDECREF (m_func); } ... but I'm not familiar with the code, so this might paper over the problem rather than fix it, I'm not sure. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-29 10:00 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 ` vries at gcc dot gnu.org [this message] 2024-01-29 10:56 ` [Bug dap/31306] " 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 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-B8Nh2DWxCk@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: linkBe 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).