public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "grazfather at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/31303] attach calls python hooks which can crash gdb
Date: Sat, 23 Nov 2024 22:57:12 +0000	[thread overview]
Message-ID: <bug-31303-4717-H1coAoWzmM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31303-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from grazfather at gmail dot com ---
Just confirmed that this issue still exists on GDB 15.2.

❯ gdb -q --nx --ex "source hook_attach.py" --ex "tar ext x:1234" --ex "attach
1608809"Remote debugging using x:1234
Attaching to process 1608809
../../gdb/thread.c:87: internal-error: inferior_thread: Assertion
`current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
---------------------
../../gdb/thread.c:87: internal-error: inferior_thread: Assertion
`current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

This is a bug, please report it.  For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.

../../gdb/thread.c:87: internal-error: inferior_thread: Assertion
`current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n

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

      parent reply	other threads:[~2024-11-23 22:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28  0:51 [Bug remote/31303] New: " grazfather at gmail dot com
2024-01-28  1:08 ` [Bug remote/31303] " grazfather at gmail dot com
2024-01-28 17:50 ` ssbssa at sourceware dot org
2024-11-23 22:57 ` grazfather at gmail dot com [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=bug-31303-4717-H1coAoWzmM@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).