public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29549] New: [gdb/selftest] selftest run_on_main_thread + ^C: terminate called without an active exception
Date: Tue, 06 Sep 2022 09:13:32 +0000 [thread overview]
Message-ID: <bug-29549-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29549
Bug ID: 29549
Summary: [gdb/selftest] selftest run_on_main_thread + ^C:
terminate called without an active exception
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
[ With gdb build from trunk of today, and with gdb-patches patch "[PATCH,v2]
[Arm] Fix endianness handling for arm record self tests" applied, which I
assume is unrelated. ]
I ran the selftests like this:
...
$ ./gdb.sh -q -batch -ex "maint selftest" | grep -i arm
...
and pressed ^C a few times.
This gave me:
...
Running selftest run_on_main_thread.
terminate called without an active exception
Fatal signal: Aborted
----- Backtrace -----
0x580e38 gdb_internal_backtrace_1
/home/vries/gdb_versions/devel/src/gdb/bt-utils.c:122
0x580edb _Z22gdb_internal_backtracev
/home/vries/gdb_versions/devel/src/gdb/bt-utils.c:168
0x7605c1 handle_fatal_signal
/home/vries/gdb_versions/devel/src/gdb/event-top.c:948
0x7fc538f76d6f ???
/usr/src/debug/glibc-2.31-150300.37.1.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x7fc538f76cdb __GI_raise
../sysdeps/unix/sysv/linux/raise.c:51
0x7fc538f78374 __GI_abort
/usr/src/debug/glibc-2.31-150300.37.1.x86_64/stdlib/abort.c:79
0x7fc5395defc5 ???
0x7fc5395ea83b ???
0x7fc5395ea8a6 ???
0xc394de _ZNSt6threadD2Ev
/usr/include/c++/7/thread:135
0xc39118 run_tests
/home/vries/gdb_versions/devel/src/gdb/unittests/main-thread-selftests.c:48
0x41be04 _ZNSt17_Function_handlerIFvvEPS0_E9_M_invokeERKSt9_Any_data
/usr/include/c++/7/bits/std_function.h:316
0x5f8095 _ZNKSt8functionIFvvEEclEv
/usr/include/c++/7/bits/std_function.h:706
0x13bc142 _ZN9selftests9run_testsEN3gdb10array_viewIKPKcEEb
/home/vries/gdb_versions/devel/src/gdbsupport/selftest.cc:100
0x8b0f96 maintenance_selftest
/home/vries/gdb_versions/devel/src/gdb/maint.c:1164
0x5d7b83 do_simple_func
/home/vries/gdb_versions/devel/src/gdb/cli/cli-decode.c:95
0x5dc933 _Z8cmd_funcP16cmd_list_elementPKci
/home/vries/gdb_versions/devel/src/gdb/cli/cli-decode.c:2543
0xbc678d _Z15execute_commandPKci
/home/vries/gdb_versions/devel/src/gdb/top.c:692
0x8a6748 catch_command_errors
/home/vries/gdb_versions/devel/src/gdb/main.c:513
0x8a6920 execute_cmdargs
/home/vries/gdb_versions/devel/src/gdb/main.c:608
0x8a7cb0 captured_main_1
/home/vries/gdb_versions/devel/src/gdb/main.c:1299
0x8a7eb3 captured_main
/home/vries/gdb_versions/devel/src/gdb/main.c:1320
0x8a7f1e _Z8gdb_mainP18captured_main_args
/home/vries/gdb_versions/devel/src/gdb/main.c:1345
0x41506d main
/home/vries/gdb_versions/devel/src/gdb/gdb.c:32
---------------------
A fatal error internal to GDB has been detected, further
debugging is not possible. GDB will now terminate.
This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.
./gdb.sh: line 35: 6508 Aborted (core dumped) $DBG $GDB -nw
-iex "add-auto-load-safe-path
/home/vries/gdb_versions/devel/build/gdb/gdb-gdb.gdb" -iex
"add-auto-load-safe-path /home/vries/gdb_versions/devel/build/gdb/gdb-gdb.py"
"${flags[@]}" "$@"
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-09-06 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 9:13 vries at gcc dot gnu.org [this message]
2022-09-06 9:14 ` [Bug gdb/29549] " vries at gcc dot gnu.org
2022-09-06 9:58 ` vries at gcc dot gnu.org
2022-09-06 10:38 ` vries at gcc dot gnu.org
2022-09-12 8:05 ` vries at gcc dot gnu.org
2022-09-12 8:06 ` vries at gcc dot gnu.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-29549-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).