Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Smith via Gdb <gdb@sourceware.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Does gdb debuginfod download libc etc.?
Date: Mon, 09 Mar 2026 17:19:44 -0400	[thread overview]
Message-ID: <ec483a582f9055456dd0591208eb148a28007381.camel@gnu.org> (raw)
In-Reply-To: <421fe2ad615c4af1443ddbd3955ee65cb7feb9ee.camel@gnu.org>

On Mon, 2026-03-09 at 16:32 -0400, Paul Smith via Gdb wrote:
> Ah, this is very useful.  Unfortunately it leads me to this
> discovery;
> the only output I get from this is:
> 
> (gdb) core-file /data/psh13/tmp/core
> [core-load] build_file_mappings: enter
> [core-load] build_file_mappings: exit

More debugging shows that linux_read_core_file_mappings() is returning
early due to this:

   /* It's not required that the NT_FILE note exists, so return silently
      if it's not found.  Beyond this point though, we'll complain
      if problems are found.  */
   asection *section = bfd_get_section_by_name (cbfd, ".note.linuxcore.file");
   if (section == nullptr)
     return;

(Most of) my core files are generated by the Google coredumper library,
not by the Linux kernel, and I guess they don't have this note section.

It appears that this note section isn't actually required in order for
us to access the build ID values (after all, elfutils does it), but
this function gives up if the section doesn't exist.

I can look into how to force my cores to have this section, but I'd
really like to teach GDB how to handle core files without it, since I
have a lot of them and will likely continue to get them for some time
even if I do manage to make this change to new releases.

  reply	other threads:[~2026-03-09 21:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 23:58 Paul Smith via Gdb
2026-03-08  9:44 ` Arsen Arsenović via Gdb
2026-03-08 21:04   ` Paul Smith via Gdb
2026-03-09  2:32     ` Simon Marchi via Gdb
2026-03-09 13:57       ` Paul Smith via Gdb
2026-03-09 15:36         ` Simon Marchi via Gdb
2026-03-09 17:28           ` Andrew Burgess via Gdb
2026-03-09 16:57         ` Andrew Burgess via Gdb
2026-03-09 20:32           ` Paul Smith via Gdb
2026-03-09 21:19             ` Paul Smith via Gdb [this message]
2026-03-10  9:12               ` Mark Wielaard
2026-03-10 14:20               ` Andrew Burgess via Gdb
2026-03-10 17:12                 ` Paul Smith via Gdb
2026-03-11  9:28                   ` Andrew Burgess via Gdb
2026-03-11 14:46                     ` Paul Smith via Gdb
2026-03-12 20:38                     ` Paul Smith via Gdb
2026-03-13 13:45                       ` Andrew Burgess via Gdb
2026-03-13 15:44                         ` Paul Smith via Gdb

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=ec483a582f9055456dd0591208eb148a28007381.camel@gnu.org \
    --to=gdb@sourceware.org \
    --cc=aburgess@redhat.com \
    --cc=psmith@gnu.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