public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "klen_s at mail dot ru" <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: Tue, 15 Mar 2022 22:14:50 +0000 [thread overview]
Message-ID: <bug-28874-4717-1rP3VcANKA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28874-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28874
Chernov Sergey aka Klen <klen_s at mail dot ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |klen_s at mail dot ru
--- Comment #10 from Chernov Sergey aka Klen <klen_s at mail dot ru> ---
yyyeeess!!!! it's work fine!
finally, you can assemble the otadchik from the trunk and test everything new!
I am about twice a week rebuilding all the tools and libraries from the trunk
and studying the errors of new features, sometimes I can help fix them. But
with this error, I could not do anything, it appeared in the trunk in October.
John Whittington, you are the best :), thank you so much!
maybe this is a crutch and something will break if the processor has two cores
or there will be another target, but here and now it works!
klen@klen-station:/klen/home/arm-kgp-eabi_@_x86_64-kgp-linux-gnu_znver3_avx2$
arm-kgp-eabi-gdb
GNU gdb
(Klen's_GNU_package_(KGP)_for_target::arm-kgp-eabi<rmprofile/lto>_host::x86_64-kgp-linux-gnu<<OXALIS>>)
12.0.50.20220315-git
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-kgp-linux-gnu --target=arm-kgp-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<klen_s@mail.ru>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) tar ext /dev/kgp/bmp
Remote debugging using /dev/kgp/bmp
(gdb) mon s
Target voltage: 0.0V
Available Targets:
No. Att Driver
1 STM32H7 M7
(gdb) att 1
Attaching to Remote target
0x0800bb2e in ?? ()
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-03-15 22:14 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 [this message]
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-1rP3VcANKA@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).