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 v6 0/4] [gdb/tui] Fix crash with debuginfod query
Date: Fri, 1 May 2026 18:34:04 +0200	[thread overview]
Message-ID: <4300deb1-765a-48fe-9d3f-69122748547d@suse.de> (raw)
In-Reply-To: <875x57fbof.fsf@redhat.com>

On 5/1/26 4:26 PM, Andrew Burgess wrote:
> Andrew Burgess <aburgess@redhat.com> writes:
> 
>> Tom de Vries <tdevries@suse.de> writes:
>>
>>> This patch series fixes two PRs, PR31449 and PR33794.
>>>
>>> An initial patch for PR31449 was submitted here [1].  A review comment
>>> reported a problem when using C-x C-a to enable TUI instead of "tui enable",
>>> not fixed by the patch.  This was filed as PR33794.
>>>
>>> The initial patch fixes PR31449 by calling a function that will force the
>>> debuginfod query to happen before enabling the TUI.
>>
>> Hi Tom,
>>
>> Just FYI, I'm not forgotten this patch.  I'm in the process of reviewing
>> it, and will have some feedback next week.
> 
> I finished looking through this series, and I couldn't shake the feeling
> that it should be possible to allow the prompt to be displayed correctly
> during the switch to TUI mode.
> 
> Fixing the 'tui enable' case is reasonably straight forward, but getting
> 'C-x C-a' to work correctly was a little harder, but I think I managed
> it in the end.
> 
> I've posted these patches as my take on this problem:
> 
>    https://inbox.sourceware.org/gdb-patches/cover.1777645161.git.aburgess@redhat.com
> 
> It would be great to hear what you think.
> 

Hi Andrew,

thanks for identifying that additional problem with 'C-x C-a' during a 
secondary prompt (patch #3).  The fix you came up with looks reasonably 
simple, and a low-risk backport to gdb-17-branch.

Patch #5 is not as trivial as the solution I proposed in this series, 
but I still think it's trivial enough to backport.

I do wonder whether patch #6 is backportable to gdb-17-branch, that 
looks a bit risky to me.

Unfortunately this is all the feedback I can provide, I'm on vacation 
for a week starting now.

Thanks,
- Tom

> Thanks,
> Andrew
> 


      reply	other threads:[~2026-05-01 16:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17  7:57 Tom de Vries
2026-04-17  7:57 ` [PATCH v6 1/4] [gdb/tui] Fix crash with debuginfod query (tui enable) Tom de Vries
2026-04-17  7:57 ` [PATCH v6 2/4] [gdb] Add debuginfod_enabled_ask_p Tom de Vries
2026-04-17  7:57 ` [PATCH v6 3/4] [gdb] Add defaulted_query_auto_answers_p Tom de Vries
2026-04-17  7:57 ` [PATCH v6 4/4] [gdb/tui] Fix crash with debuginfod query (C-x C-a) Tom de Vries
2026-04-25 14:40 ` [PATCH v6 0/4] [gdb/tui] Fix crash with debuginfod query Andrew Burgess
2026-05-01 14:26   ` Andrew Burgess
2026-05-01 16:34     ` Tom de Vries [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=4300deb1-765a-48fe-9d3f-69122748547d@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