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: Thu, 16 Apr 2026 11:28:46 -0400 [thread overview]
Message-ID: <58629ee1c12407ec1768c1f7ed397ec96875d155.camel@gnu.org> (raw)
In-Reply-To: <87342690kz.fsf@redhat.com>
On Wed, 2026-03-11 at 09:28 +0000, Andrew Burgess wrote:
> Paul Smith <psmith@gnu.org> writes:
>
> > On Tue, 2026-03-10 at 14:20 +0000, Andrew Burgess wrote:
> > > Attached below is a **VERY** rough patch which might get things
> > > going for you.
> >
> > ... your patch works for me
>
> I started working on cleaning up the patch ready for submission to
> master, but I'm pretty busy for the next few days, so it'll probably
> be next week now before I post anything.
I don't need any updates to these changes: what I have is working for
me in GDB, and I also added facilities to Google Coredumper to add an
NT_FILE section to generated coredumps [1].
But, I was wondering if this change is intending to be queued for the
next release of GDB?
Cheers!
[1] https://github.com/madscientist/google-coredumper/commit/d61b7b5d8e91e5c184425c35c6b5ebeac7b60da4
prev parent reply other threads:[~2026-04-16 15:29 UTC|newest]
Thread overview: 19+ 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
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
2026-04-16 15:28 ` Paul Smith via Gdb [this message]
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=58629ee1c12407ec1768c1f7ed397ec96875d155.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