public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <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: Sun, 17 Mar 2024 22:01:33 +0000	[thread overview]
Message-ID: <bug-31497-4717-DyT0YSF5vZ@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 #3 from Tom Tromey <tromey at sourceware dot org> ---
Re-reading is no problem, section::read is idempotent.

I wonder if we have enough information to write a test case.
From the stack trace I'd guess this is happening during
symtab expansion.  So the core file shouldn't be needed,
it might reproduce with just any old small test case with
the appropriate compiler & flags, and "gdb -readnow"...

If you want to send it as a gdb patch, see:
https://sourceware.org/gdb/wiki/ContributionChecklist

FWIW I think gdb should move away from lazily reading
section info and back toward reading it when the file is
opened.  This would also eliminate this bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-03-17 22:01 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 [this message]
2024-03-18 18:05 ` sungdgdhtryrt at gmail dot com
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-DyT0YSF5vZ@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: link
Be 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).