public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "gdbsourceware.3k5z5 at passmail dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28874] arm-none-eabi: internal-error: thread_info* inferior_thread(): Assertion `current_thread_ != nullptr' failed
Date: Wed, 06 Sep 2023 04:08:03 +0000 [thread overview]
Message-ID: <bug-28874-4717-zcERmNdjp0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28874-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28874
fidgetingbits <gdbsourceware.3k5z5 at passmail dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gdbsourceware.3k5z5@passmai
| |l.net
--- Comment #19 from fidgetingbits <gdbsourceware.3k5z5 at passmail dot net> ---
I run into this same issue on the latest version of gdb (13.2 at the time of
writing) and gdbserver when debugging various remote 32-bit ARM targets,
specifically when using
pwndbg loaded (sets up various event hooks).
Also worth noting that after gdb crashes, if you restart gdb and re-attach a
second time without restarting the target process, the attach works correctly.
My solution has always been to just automatically restart gdb on crash and
re-attach from a shell script.
I've confirmed that using the patch provided by John Whittington addresses the
problem.
Would be nice to get this fixed as pwndbg users wishing to remotely debug an
ARM target will run into this issue.
Happy to provide any debug information needed.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-09-06 4:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 7:49 [Bug gdb/28874] New: " git at jbrengineering dot co.uk
2022-02-09 7:49 ` [Bug gdb/28874] " git at jbrengineering dot co.uk
2022-02-09 8:18 ` git at jbrengineering dot co.uk
2022-02-19 8:48 ` me at ruff dot mobi
2022-03-06 17:02 ` tromey at sourceware dot org
2022-03-06 20:12 ` me at ruff dot mobi
2022-03-06 20:20 ` me at ruff dot mobi
2022-03-06 20:27 ` tromey at sourceware dot org
2022-03-06 20:31 ` me at ruff dot mobi
2022-03-06 20:33 ` me at ruff dot mobi
2022-03-09 15:02 ` git at jbrengineering dot co.uk
2022-03-09 15:32 ` git at jbrengineering dot co.uk
2022-03-09 15:46 ` git at jbrengineering dot co.uk
2022-03-15 22:14 ` klen_s at mail dot ru
2022-03-17 16:10 ` git at jbrengineering dot co.uk
2022-03-17 21:25 ` klen_s at mail dot ru
2022-03-18 21:18 ` tromey at sourceware dot org
2022-03-27 16:16 ` mikaela.szekely at qyriad dot me
2022-05-22 23:58 ` jj at stusta dot net
2022-07-13 13:53 ` git at jbrengineering dot co.uk
2022-07-15 12:50 ` mikaela.szekely at qyriad dot me
2022-07-21 8:21 ` git at jbrengineering dot co.uk
2022-10-21 10:08 ` luis.machado at arm dot com
2023-09-06 4:08 ` gdbsourceware.3k5z5 at passmail dot net [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-28874-4717-zcERmNdjp0@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).