public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/29277] jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed with separate debug files Date: Mon, 01 Aug 2022 13:46:14 +0000 [thread overview] Message-ID: <bug-29277-4717-s4ilScz5KG@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29277-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29277 --- Comment #3 from Andreas Schwab <schwab@linux-m68k.org> --- I'm seeing this on riscv64: $ gdb/gdb --args qemu-riscv64 /usr/bin/cat GNU gdb (GDB) 13.0.50.20220801-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 "riscv64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. 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"... Reading symbols from qemu-riscv64... Reading symbols from /usr/lib/debug/usr/bin/qemu-riscv64-7.0.0-82.1.riscv64.debug... (gdb) r Starting program: /usr/bin/qemu-riscv64 /usr/bin/cat [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/lp64d/libthread_db.so.1". [New Thread 0x3ff7ffb3c0 (LWP 1363)] ../../gdb/gdb/jit.c:1247: internal-error: jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. ----- Backtrace ----- 0x8c5cd gdb_internal_backtrace_1 ../../gdb/gdb/bt-utils.c:122 0x8c5cd _Z22gdb_internal_backtracev ../../gdb/gdb/bt-utils.c:168 0x330621 internal_vproblem ../../gdb/gdb/utils.c:396 0x3307f5 _Z15internal_verrorPKciS0_Pv ../../gdb/gdb/utils.c:476 0x3b50cd _Z14internal_errorPKciS0_z ../../gdb/gdbsupport/errors.cc:55 0x1a9cfd _Z17jit_event_handlerP7gdbarchP7objfile ../../gdb/gdb/jit.c:1247 0x7b1b5 handle_jit_event ../../gdb/gdb/breakpoint.c:5672 0x7b1b5 _Z20bpstat_run_callbacksP6bpstat ../../gdb/gdb/breakpoint.c:5875 0x19ef05 process_event_stop_test ../../gdb/gdb/infrun.c:6651 0x1a22eb handle_stop_requested ../../gdb/gdb/infrun.c:4627 0x1a22eb handle_stop_requested ../../gdb/gdb/infrun.c:4622 0x1a22eb handle_inferior_event ../../gdb/gdb/infrun.c:5883 0x1a3c0d _Z20fetch_inferior_eventv ../../gdb/gdb/infrun.c:4233 0x3b53c9 gdb_wait_for_event ../../gdb/gdbsupport/event-loop.cc:692 0x3b585d _Z16gdb_do_one_eventv ../../gdb/gdbsupport/event-loop.cc:210 0x1d5a29 start_event_loop ../../gdb/gdb/main.c:411 0x1d5a29 captured_command_loop ../../gdb/gdb/main.c:471 0x1d70e9 captured_main ../../gdb/gdb/main.c:1329 0x1d70e9 _Z8gdb_mainP18captured_main_args ../../gdb/gdb/main.c:1344 0x21137 main ../../gdb/gdb/gdb.c:32 --------------------- ../../gdb/gdb/jit.c:1247: internal-error: jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed. (top-gdb) p jit_bp_sym.objfile.jiter_data $2 = { _M_t = {<std::__uniq_ptr_impl<jiter_objfile_data, std::default_delete<jiter_objfile_data> >> = { _M_t = {<std::_Tuple_impl<0, jiter_objfile_data*, std::default_delete<jiter_objfile_data> >> = {<std::_Tuple_impl<1, std::default_delete<jiter_objfile_data> >> = {<std::_Head_base<1, std::default_delete<jiter_objfile_data>, true>> = {_M_head_impl = {<No data fields>}}, <No data fields>}, <std::_Head_base<0, jiter_objfile_data*, false>> = { _M_head_impl = 0x0}, <No data fields>}, <No data fields>}}, <No data fields>}} (top-gdb) p jit_bp_sym.objfile.separate_debug_objfile_backlink.jiter_data $5 = { _M_t = {<std::__uniq_ptr_impl<jiter_objfile_data, std::default_delete<jiter_objfile_data> >> = { _M_t = {<std::_Tuple_impl<0, jiter_objfile_data*, std::default_delete<jiter_objfile_data> >> = {<std::_Tuple_impl<1, std::default_delete<jiter_objfile_data> >> = {<std::_Head_base<1, std::default_delete<jiter_objfile_data>, true>> = {_M_head_impl = {<No data fields>}}, <No data fields>}, <std::_Head_base<0, jiter_objfile_data*, false>> = { _M_head_impl = 0xa9f8e0}, <No data fields>}, <No data fields>}}, <No data fields>}} -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-01 13:46 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-22 19:20 [Bug breakpoints/29277] New: " guillaume at morinfr dot org 2022-06-23 13:44 ` [Bug breakpoints/29277] " vries at gcc dot gnu.org 2022-06-27 14:06 ` hector.oron at gmail dot com 2022-07-19 14:23 ` vries at gcc dot gnu.org 2022-08-01 13:46 ` schwab@linux-m68k.org [this message] 2022-08-01 15:55 ` vries at gcc dot gnu.org 2022-08-01 15:56 ` vries at gcc dot gnu.org 2022-08-01 16:46 ` vries at gcc dot gnu.org 2022-10-13 13:40 ` vries at gcc dot gnu.org 2023-12-16 15:24 ` ssbssa at sourceware dot org 2023-12-16 15:36 ` 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-29277-4717-s4ilScz5KG@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).