public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "me at ruff dot mobi" <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: Sun, 06 Mar 2022 20:12:57 +0000	[thread overview]
Message-ID: <bug-28874-4717-dkEov9uFQU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28874-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Ruslan N. Marchenko <me at ruff dot mobi> ---
In my case executable is irrelevant, you can simply have none at all.
Just need a remote debugger (I use BMP) and then as simple as 
$ arm-none-eabi-gdb
GNU gdb (GDB) 11.2
Copyright (C) 2022 Free Software Foundation, Inc.
...
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) tar ext /dev/ttyACM0
Remote debugging using /dev/ttyACM0
(gdb) mon s
Target voltage: 3.29V
Available Targets:
No. Att Driver
 1      STM32L47x M4
(gdb) set debug remote on
(gdb) attach 1
Attaching to Remote target
[remote] Sending packet: $vAttach;1#37
[remote] Received Ack
[remote] Packet received: T05
[remote] packet_ok: Packet vAttach (attach) is supported
[remote] Sending packet: $qC#b4
[remote] Received Ack
[remote] Packet received:
../../gdb/thread.c:72: internal-error: thread_info* 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)

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

  parent reply	other threads:[~2022-03-06 20:12 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 [this message]
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

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-dkEov9uFQU@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).