public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sungdgdhtryrt at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31497] gdb internal fatal error while opening a core dump; binary built with '-gsplit-dwarf' Date: Mon, 18 Mar 2024 18:05:23 +0000 [thread overview] Message-ID: <bug-31497-4717-xfl1yMbdLP@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31497-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31497 --- Comment #4 from Hans <sungdgdhtryrt at gmail dot com> --- Indeed the core file is not necessary to provoke the bug. Here is a minimal setup for the bug to occur. cat > main.cpp << EOF #include <stdio.h> int main() { printf("hello world\n"); return 0; } EOF clang++-16 -g -gsplit-dwarf -c main.cpp -o main.o clang++-16 main.o -o main llvm-dwp-16 -e main -o main.dwp <path to custom built gdb> ./main clang++-16 tooling uses dwarf version 5 by default. The "--readnow" option is not necessary. Thank you again for the hint. I will try to send a gdb patch for this. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-18 18:05 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-16 7:42 [Bug gdb/31497] New: " sungdgdhtryrt at gmail dot com 2024-03-16 16:17 ` [Bug gdb/31497] " tromey at sourceware dot org 2024-03-17 4:01 ` sam at gentoo dot org 2024-03-17 7:37 ` sungdgdhtryrt at gmail dot com 2024-03-17 22:01 ` tromey at sourceware dot org 2024-03-18 18:05 ` sungdgdhtryrt at gmail dot com [this message] 2024-03-19 13:18 ` tromey at sourceware dot 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-31497-4717-xfl1yMbdLP@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).