Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/tui] Fix crash with debuginfod query
Date: Fri, 16 Jan 2026 14:24:39 +0100	[thread overview]
Message-ID: <236007c6-b879-4f48-856c-fe38e370919d@suse.de> (raw)
In-Reply-To: <ce7c8f09-2023-48a1-80c1-999a2b5ae9b6@suse.de>

On 1/15/26 2:04 PM, Tom de Vries wrote:
>> haven't looked into what's going wrong, but the test appears to hang
>> at the "Enable debuginfod for this session? (y or [n])" prompt for a
>> significant period of time.
>>
>> I ran the test a small number of times, and this behaviour seems
>> repeatable.
> 
> Hi Andrew,
> 
> Thanks for the review.
> 
> I think what is happening for me on openSUSE Leap 16.0, is that the 
> executable does contains debuginfo for some compilation units, though 
> not for the CU contaning main.
> 
> Consequently, the file command doesn't trigger the query, but 
> atttempting to display main does.
> 
> Conversely, on Fedora, the executable contains no debuginfo, and the 
> query triggers on the file command.
> 
> I'll fix the test-case to get the same behaviour on both distros.

To come back to this, the problem turned out to be slightly different, 
and I ended up making a setup similar to gdb.tui/tui-missing-src.exp.

Thanks,
- Tom

  reply	other threads:[~2026-01-16 13:25 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 [this message]
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
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=236007c6-b879-4f48-856c-fe38e370919d@suse.de \
    --to=tdevries@suse.de \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@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