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] New: attach calls python hooks which can crash gdb
Date: Sun, 28 Jan 2024 00:51:11 +0000	[thread overview]
Message-ID: <bug-31303-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31303
           Summary: attach calls python hooks which can crash gdb
           Product: gdb
           Version: 13.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: remote
          Assignee: unassigned at sourceware dot org
          Reporter: grazfather at gmail dot com
  Target Milestone: ---

Created attachment 15337
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15337&action=edit
stacktrace

On GDB 13.2, when debugging a target using `target extended-remote` with a
continue hook setup which tries to get the selected frame, when I `attach 1`,
this hook is called and gdb crashes with a failed assertion.

../../gdb/thread.c:85: internal-error: inferior_thread: Assertion
`current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,

This hook does not seem to be called when I attach to a local process (by pid).

Stack trace is attached.

I reproduce with a blackmagic probe connected to a tty.

.gdbinit:

source hook_continue.py
target extended-remote /dev/cu.usbmodel72AE15F41
monitor tpwr enable
monitor swdp_scan
attach 1

hook_continue.py:

def f(_):
    gdb.selected_frame()
                                                                               
                                                    gdb.events.cont.connect(f)

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

             reply	other threads:[~2024-01-28  0:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28  0:51 grazfather at gmail dot com [this message]
2024-01-28  1:08 ` [Bug remote/31303] " grazfather at gmail dot com
2024-01-28 17:50 ` ssbssa at sourceware 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-31303-4717@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).