Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess via Gdb <gdb@sourceware.org>
To: psmith@gnu.org
Cc: gdb@sourceware.org
Subject: Re: Does gdb debuginfod download libc etc.?
Date: Wed, 11 Mar 2026 09:28:44 +0000	[thread overview]
Message-ID: <87342690kz.fsf@redhat.com> (raw)
In-Reply-To: <96dde02ef4f1d88779de1eebb5277a7258fadf46.camel@gnu.org>

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.  This patch applies on gdb-17-branch and includes the
>> previous changes I sent, so you should probably revert them and then
>> try this patch to avoid conflicts.
>
> Wow I did not expect such a quick response!  However, your patch works
> for me (I fully grok your admonitions about this being a rough draft).
> I did see odd output related to operator() but maybe it's not odd to
> you :)

Glad this is unblocking you.  The operator() stuff is fine, it's just
because the debug is being emitted from within a C++ lambda function.

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.

However, I'm not sure if this would ever be back-ported to the
gdb-17-branch, this isn't a regression or bug fix, handling a missing
NT_FILE note has never worked in GDB, so this is really a new
functionality patch, which would normally only be applied to master.

Thanks,
Andrew


  reply	other threads:[~2026-03-11  9:29 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
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 [this message]
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=87342690kz.fsf@redhat.com \
    --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