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] [gdb/selftest] selftest run_on_main_thread + ^C: terminate called without an active exception
Date: Tue, 06 Sep 2022 09:14:50 +0000	[thread overview]
Message-ID: <bug-29549-4717-LjN2guvhJg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29549-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
From the core file we get a bit more specific backtrace:
...
#0  raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00000000007606a6 in handle_fatal_signal (sig=6)
    at /home/vries/gdb_versions/devel/src/gdb/event-top.c:971
#2  <signal handler called>
#3  __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#4  0x00007f2dbd731375 in __GI_abort () at abort.c:79
#5  0x00007f2dbdd97fc6 in ?? () from /usr/lib64/libstdc++.so.6
#6  0x00007f2dbdda383c in ?? () from /usr/lib64/libstdc++.so.6
#7  0x00007f2dbdda38a7 in std::terminate() () from /usr/lib64/libstdc++.so.6
#8  0x0000000000c394df in std::thread::~thread (this=0x7ffe5ffacb80, 
    __in_chrg=<optimized out>) at /usr/include/c++/7/thread:135
#9  0x0000000000c39119 in selftests::main_thread_tests::run_tests ()
    at
/home/vries/gdb_versions/devel/src/gdb/unittests/main-thread-selftests.c:48
#10 0x000000000041be05 in std::_Function_handler<void (), void
(*)()>::_M_invoke(std::_Any_data const&) (__functor=...) at
/usr/include/c++/7/bits/std_function.h:316
#11 0x00000000005f8096 in std::function<void ()>::operator()() const
(this=0x3fadf90)
    at /usr/include/c++/7/bits/std_function.h:706
#12 0x00000000013bc143 in selftests::run_tests (filters=..., verbose=false)
    at /home/vries/gdb_versions/devel/src/gdbsupport/selftest.cc:100
#13 0x00000000008b0f97 in maintenance_selftest (args=0x7ffe5ffae141
"run_on_main_thread", 
...

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

  reply	other threads:[~2022-09-06  9:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06  9:13 [Bug gdb/29549] New: " vries at gcc dot gnu.org
2022-09-06  9:14 ` vries at gcc dot gnu.org [this message]
2022-09-06  9:58 ` [Bug gdb/29549] " 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-LjN2guvhJg@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).