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 symtab/26797] New: [readnow] Dwarf error result in no minimal symbols Date: Wed, 28 Oct 2020 09:14:57 +0000 [thread overview] Message-ID: <bug-26797-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26797 Bug ID: 26797 Summary: [readnow] Dwarf error result in no minimal symbols Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- Normally we have: ... (gdb) file dw2-error^M Reading symbols from dw2-error...^M Dwarf Error: wrong version in compilation unit header (is 153, should be 2, 3, 4 or 5) [in module dw2-error]^M (No debugging symbols found in dw2-error)^M (gdb) PASS: gdb.dwarf2/dw2-error.exp: file dw2-error break -q main^M Breakpoint 1 at 0x4004ab^M (gdb) PASS: gdb.dwarf2/dw2-error.exp: break -q main ... But with with -readnow, we have instead: ... (gdb) file dw2-error^M Reading symbols from dw2-error...^M Dwarf Error: wrong version in compilation unit header (is 153, should be 2, 3, 4 or 5) [in module dw2-error]^M (gdb) PASS: gdb.dwarf2/dw2-error.exp: file dw2-error break -q main^M No symbol table is loaded. Use the "file" command.^M (gdb) FAIL: gdb.dwarf2/dw2-error.exp: break -q main ... So, with -readnow, we somehow also end up without minimal symbols. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-10-28 9:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-28 9:14 vries at gcc dot gnu.org [this message] 2020-10-31 18:23 ` [Bug symtab/26797] " tromey at sourceware dot org 2023-09-08 10:27 ` cvs-commit at gcc dot gnu.org 2023-11-06 7:54 ` 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-26797-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).