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 gdb/29680] New: ../../gdb/gdb/jit.c:1247: internal-error: jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed. Date: Thu, 13 Oct 2022 08:15:25 +0000 [thread overview] Message-ID: <bug-29680-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29680 Bug ID: 29680 Summary: ../../gdb/gdb/jit.c:1247: internal-error: jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed. Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: schwab@linux-m68k.org Target Milestone: --- Host: x86_64-*-* Trying to debug qemu from <https://download.opensuse.org/repositories/home:/Andreas_Schwab:/qemu/standard/>: $ gdb --args qemu-riscv64 ./bash GNU gdb (GDB) 13.0.50.20221013-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 "x86_64-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.1.0-20.1.x86_64.debug... (gdb) r Starting program: /usr/bin/qemu-riscv64 ./bash [New LWP 24170] ../../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 ----- 0x4d3f01 gdb_internal_backtrace_1 ../../gdb/gdb/bt-utils.c:122 0x4d3f01 _Z22gdb_internal_backtracev ../../gdb/gdb/bt-utils.c:168 0x89ec14 internal_vproblem ../../gdb/gdb/utils.c:396 0x89edf8 _Z15internal_verrorPKciS0_P13__va_list_tag ../../gdb/gdb/utils.c:476 0x98f2b1 _Z14internal_errorPKciS0_z ../../gdb/gdbsupport/errors.cc:58 0x6b6e14 _Z17jit_event_handlerP7gdbarchP7objfile ../../gdb/gdb/jit.c:1247 0x4bc714 handle_jit_event ../../gdb/gdb/breakpoint.c:5688 0x4bc714 _Z20bpstat_run_callbacksP6bpstat ../../gdb/gdb/breakpoint.c:5891 0x6a0fd5 process_event_stop_test ../../gdb/gdb/infrun.c:6651 0x6a53ab handle_signal_stop ../../gdb/gdb/infrun.c:6619 0x6a68e8 handle_inferior_event ../../gdb/gdb/infrun.c:5869 0x6a7f15 _Z20fetch_inferior_eventv ../../gdb/gdb/infrun.c:4233 0x98fd1c gdb_wait_for_event ../../gdb/gdbsupport/event-loop.cc:695 0x99045e _Z16gdb_do_one_eventi ../../gdb/gdbsupport/event-loop.cc:217 0x6f2ade start_event_loop ../../gdb/gdb/main.c:411 0x6f2ade captured_command_loop ../../gdb/gdb/main.c:471 0x6f4424 captured_main ../../gdb/gdb/main.c:1330 0x6f4424 _Z8gdb_mainP18captured_main_args ../../gdb/gdb/main.c:1345 0x41c2b4 main ../../gdb/gdb/gdb.c:32 --------------------- ../../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. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-10-13 8:15 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-13 8:15 schwab@linux-m68k.org [this message] 2022-10-13 13:37 ` [Bug breakpoints/29680] " schwab@linux-m68k.org 2022-10-13 13:40 ` 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-29680-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).