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 dap/31306] New: [gdb/dap] segfault in new_threadstate during gdb.dap/eof.exp Date: Mon, 29 Jan 2024 06:49:24 +0000 [thread overview] Message-ID: <bug-31306-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31306 Bug ID: 31306 Summary: [gdb/dap] segfault in new_threadstate during gdb.dap/eof.exp Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: dap Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- I noticed after doing a full test run on aarch64-linux that I was left with two core files. One of them is from the gdb internal error in gdb.threads/detach-step-over.exp, which triggers regularly (but not always) for me. The other one I couldn't relate back to a test-case, so I did another run which lists the build/gdb/testsuite dir after each test, which suggested the core is generated by gdb.dap/eof.exp. The backtrace looks like: ... (gdb) bt #0 0x0000ffff76e92280 in __pthread_kill_implementation () from /lib64/libc.so.6 #1 0x0000ffff76e45800 [PAC] in raise () from /lib64/libc.so.6 #2 0x00000000007aeeb0 [PAC] in handle_fatal_signal (sig=11) at /home/vries/gdb/src/gdb/event-top.c:926 #3 0x00000000007aef38 in handle_sigsegv (sig=11) at /home/vries/gdb/src/gdb/event-top.c:976 #4 <signal handler called> #5 0x0000ffff7780db14 in new_threadstate () from /lib64/libpython3.12.so.1.0 #6 0x0000ffff77870548 [PAC] in PyGILState_Ensure () from /lib64/libpython3.12.so.1.0 #7 0x0000000000a6adf0 [PAC] in gdbpy_gil::gdbpy_gil (this=0xffffd6b572a8) at /home/vries/gdb/src/gdb/python/python-internal.h:787 #8 0x0000000000ab6568 in gdbpy_event::~gdbpy_event (this=0xffff3c001e80, __in_chrg=<optimized out>) at /home/vries/gdb/src/gdb/python/python.c:1051 #9 0x0000000000ab721c in std::_Function_base::_Base_manager<gdbpy_event>::_M_destroy ( __victim=...) at /usr/include/c++/13/bits/std_function.h:175 #10 0x0000000000ab7098 in std::_Function_base::_Base_manager<gdbpy_event>::_M_manager ( __dest=..., __source=..., __op=std::__destroy_functor) at /usr/include/c++/13/bits/std_function.h:203 --Type <RET> for more, q to quit, c to continue without paging--c #11 0x0000000000ab6cd0 in std::_Function_handler<void (), gdbpy_event>::_M_manager(std::_Any_data&, std::_Any_data const&, std::_Manager_operation) (__dest=..., __source=..., __op=std::__destroy_functor) at /usr/include/c++/13/bits/std_function.h:282 #12 0x000000000042dd9c in std::_Function_base::~_Function_base (this=0xffff3c001bb0, __in_chrg=<optimized out>) at /usr/include/c++/13/bits/std_function.h:244 #13 0x000000000042e654 in std::function<void ()>::~function() (this=0xffff3c001bb0, __in_chrg=<optimized out>) at /usr/include/c++/13/bits/std_function.h:334 #14 0x0000000000b66c30 in std::_Destroy<std::function<void ()> >(std::function<void ()>*) (__pointer=0xffff3c001bb0) at /usr/include/c++/13/bits/stl_construct.h:151 #15 0x0000000000b66aa0 in std::_Destroy_aux<false>::__destroy<std::function<void ()>*>(std::function<void ()>*, std::function<void ()>*) (__first=0xffff3c001bb0, __last=0xffff3c001bd0) at /usr/include/c++/13/bits/stl_construct.h:163 #16 0x0000000000b667a8 in std::_Destroy<std::function<void ()>*>(std::function<void ()>*, std::function<void ()>*) (__first=0xffff3c001bb0, __last=0xffff3c001bd0) at /usr/include/c++/13/bits/stl_construct.h:196 #17 0x0000000000b661e4 in std::_Destroy<std::function<void ()>*, std::function<void ()> >(std::function<void ()>*, std::function<void ()>*, std::allocator<std::function<void ()> >&) (__last=0xffff3c001bd0, __first=0xffff3c001bb0) at /usr/include/c++/13/bits/alloc_traits.h:948 #18 std::vector<std::function<void ()>, std::allocator<std::function<void ()> > >::~vector() (this=0x2a183c8 <runnables>, __in_chrg=<optimized out>) at /usr/include/c++/13/bits/stl_vector.h:732 #19 0x0000ffff76e48370 in __run_exit_handlers () from /lib64/libc.so.6 #20 0x0000ffff76e48450 [PAC] in exit () from /lib64/libc.so.6 #21 0x0000000000c933dc [PAC] in quit_force (exit_arg=0x0, from_tty=0) at /home/vries/gdb/src/gdb/top.c:1826 #22 0x0000000000607b44 in quit_command (args=0x0, from_tty=0) at /home/vries/gdb/src/gdb/cli/cli-cmds.c:508 #23 0x0000000000c90480 in quit_cover () at /home/vries/gdb/src/gdb/top.c:304 #24 0x00000000007af49c in async_disconnect (arg=0x0) at /home/vries/gdb/src/gdb/event-top.c:1230 #25 0x00000000005474fc in invoke_async_signal_handlers () at /home/vries/gdb/src/gdb/async-event.c:234 #26 0x000000000157af8c in gdb_do_one_event (mstimeout=-1) at /home/vries/gdb/src/gdbsupport/event-loop.cc:199 #27 0x0000000000941898 in start_event_loop () at /home/vries/gdb/src/gdb/main.c:401 #28 0x0000000000941a10 in captured_command_loop () at /home/vries/gdb/src/gdb/main.c:465 #29 0x0000000000943490 in captured_main (data=0xffffd6b57878) at /home/vries/gdb/src/gdb/main.c:1335 #30 0x0000000000943514 in gdb_main (args=0xffffd6b57878) at /home/vries/gdb/src/gdb/main.c:1354 #31 0x0000000000423ab4 in main (argc=14, argv=0xffffd6b57a08) at /home/vries/gdb/src/gdb/gdb.c:39 ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-01-29 6:49 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-29 6:49 vries at gcc dot gnu.org [this message] 2024-01-29 10:00 ` [Bug dap/31306] " vries at gcc dot gnu.org 2024-01-29 10:56 ` vries at gcc dot gnu.org 2024-01-29 11:53 ` vries at gcc dot gnu.org 2024-01-29 11:54 ` vries at gcc dot gnu.org 2024-01-29 17:20 ` tromey at sourceware dot org 2024-01-29 21:18 ` vries at gcc dot gnu.org 2024-02-05 16:24 ` vries at gcc dot gnu.org 2024-02-07 9:03 ` vries at gcc dot gnu.org 2024-02-12 18:58 ` tromey at sourceware dot org 2024-02-14 17:24 ` cvs-commit at gcc dot gnu.org 2024-02-14 17:25 ` 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-31306-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: linkBe 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).