From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH] [gdb/tui] Fix crash with debuginfod query
Date: Fri, 16 Jan 2026 16:07:16 +0100 [thread overview]
Message-ID: <5a4734a0-95f4-4d8d-9d8a-1470a2b17423@suse.de> (raw)
In-Reply-To: <87fr85ehi8.fsf@tromey.com>
On 1/16/26 3:53 PM, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>
> Tom> PR tui/31449 reports a SIGFPE when the debuginfod query happens while enabling
> Tom> TUI using the "tui enable" command:
>
> What if we just got rid of the query and debuginfod was either on or off.
I'm not necessarily against that.
But we've already released gdb versions that support this, and I need a
patch to backport.
Thanks,
- Tom
next prev parent reply other threads:[~2026-01-16 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 17:28 Tom de Vries
2026-01-15 11:29 ` Andrew Burgess
2026-01-15 13:04 ` Tom de Vries
2026-01-16 13:24 ` Tom de Vries
2026-01-15 12:13 ` Andrew Burgess
2026-01-15 13:13 ` Tom de Vries
2026-01-15 14:26 ` Tom de Vries
2026-01-16 13:25 ` Tom de Vries
2026-01-16 14:53 ` Tom Tromey
2026-01-16 15:07 ` Tom de Vries [this message]
2026-01-17 13:14 ` Andrew Burgess
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=5a4734a0-95f4-4d8d-9d8a-1470a2b17423@suse.de \
--to=tdevries@suse.de \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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