public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "eigelc at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug rust/29550] New: Segmentation fault in infrun.c Date: Tue, 06 Sep 2022 09:55:45 +0000 [thread overview] Message-ID: <bug-29550-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29550 Bug ID: 29550 Summary: Segmentation fault in infrun.c Product: gdb Version: 12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: rust Assignee: unassigned at sourceware dot org Reporter: eigelc at gmail dot com Target Milestone: --- I am debugging a rather complex rust application. gdb crashes. (gdb) set follow-fork-mode child (gdb) b src/runtime/fork/init/mod.rs:150 Breakpoint 1 at 0x559ebe2aab9d: file mod.rs, line 150. (gdb) c Continuing. [Attaching after Thread 0x7fdec5453cc0 (LWP 28777) fork to child process 46624] [New inferior 2 (process 46624)] [Detaching after fork from parent process 28777] [Inferior 1 (process 28777) detached] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Attaching after Thread 0x7fdec5453cc0 (LWP 46624) fork to child process 46625] [New inferior 3 (process 46625)] [Detaching after fork from parent process 46624] [Inferior 2 (process 46624) detached] warning: Target and debugger are in different PID namespaces; thread lists and other data are likely unreliable. Connect to gdbserver inside the container. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Attaching after Thread 0x7fdec5453cc0 (LWP 46625) fork to child process 46626] [New inferior 4 (process 46626)] Fatal signal: Segmentation fault ----- Backtrace ----- 0x562325f90c20 gdb_internal_backtrace_1 /home/cristianeigel/tmp/gdb-12.1/gdb/bt-utils.c:122 0x562325f90c20 _Z22gdb_internal_backtracev /home/cristianeigel/tmp/gdb-12.1/gdb/bt-utils.c:168 0x5623260931f9 handle_fatal_signal /home/cristianeigel/tmp/gdb-12.1/gdb/event-top.c:904 0x5623260933b8 handle_sigsegv /home/cristianeigel/tmp/gdb-12.1/gdb/event-top.c:977 0x7f53b8ee151f ??? ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0 0x5623260fb6c7 maybe_set_commit_resumed_all_targets /home/cristianeigel/tmp/gdb-12.1/gdb/infrun.c:2785 0x562325ed4d42 _ZN29scoped_disable_commit_resumed5resetEv /home/cristianeigel/tmp/gdb-12.1/gdb/infrun.c:2895 0x562325ed4d42 _ZN29scoped_disable_commit_resumedD4Ev /home/cristianeigel/tmp/gdb-12.1/gdb/infrun.c:2927 0x562325ed4d42 _Z20fetch_inferior_eventv /home/cristianeigel/tmp/gdb-12.1/gdb/infrun.c:4151 0x562326425395 gdb_wait_for_event /home/cristianeigel/tmp/gdb-12.1/gdbsupport/event-loop.cc:700 0x562326425879 gdb_wait_for_event /home/cristianeigel/tmp/gdb-12.1/gdbsupport/event-loop.cc:596 0x562326425879 _Z16gdb_do_one_eventv /home/cristianeigel/tmp/gdb-12.1/gdbsupport/event-loop.cc:212 0x562326152d64 start_event_loop /home/cristianeigel/tmp/gdb-12.1/gdb/main.c:421 0x562326152d64 captured_command_loop /home/cristianeigel/tmp/gdb-12.1/gdb/main.c:481 0x562326154964 captured_main /home/cristianeigel/tmp/gdb-12.1/gdb/main.c:1351 0x562326154964 _Z8gdb_mainP18captured_main_args /home/cristianeigel/tmp/gdb-12.1/gdb/main.c:1366 0x562325ee87ff main /home/cristianeigel/tmp/gdb-12.1/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/>. [1] 46554 segmentation fault sudo -E /home/cristianeigel/.cargo/bin/rust-gdb --pid 28777 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-09-06 9:55 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-06 9:55 eigelc at gmail dot com [this message] 2022-09-07 14:23 ` [Bug rust/29550] " simon.marchi at polymtl dot ca 2022-09-08 8:31 ` eigelc at gmail dot com 2022-09-08 15:29 ` simon.marchi at polymtl dot ca
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-29550-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).