From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 00DC43858D39; Wed, 1 Feb 2023 00:03:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 00DC43858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675209835; bh=Bf6hoMJkpxvWKhQIulCuWKIsKa2jxdH9ZiiPdkDYIyg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZVxdl/xPDH6dTPhQ/KxGKXp8WVWalghVRmAp29eZgX0UinMhDffq6BqrqIzLv3BBT R7moHwj96K1OsN0V/tUkpcgk+gJGewZHX2jYxuCGuzVdtuIUWzuWwzvLEWrmBqt6xW aTacfITVns1XpSV6jJka4VyZ4RgBBdHUHL24xupk= From: "amerey at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/29251] gdb stuck asking to enable debuginfod Date: Wed, 01 Feb 2023 00:03:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 11.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: amerey at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29251 --- Comment #5 from Aaron Merey --- (In reply to Chad Cassady from comment #4)=20 > I'm able to reproduce this by using gdb's machine interface (-i=3Dmi). No > matter what I type into emacs' client (gud), it asks me to choose between > yes and no.=20 >=20 > To reproduce, I start the debugger in emacs and ask it to invoke gdb like > this: > coredumpctl --debugger-arguments=3D'-i=3Dmi' debug >=20 > I am unable to use the editor client to debug this way. So I just run it = in > a terminal. >=20 > I suspect the interactive feature to confirm debuginfo downloads was not= =20 > developed to account for the machine interface, but have not done additio= nal > research to validate this hypothesis. I also do not know what role, if an= y, > coredumpctl plays in handling the I/O to the gdb process, but I'm assuming > it just invokes GDB with the core file and gets out of the way. >=20 > I am happy to conduct further investigation if someone is working on this. Hi Chad, thanks for the reproducer. When I run=20 M-x gdb RET coredumpctl --debugger-arguments=3D'-i=3Dmi' debug it looks like emacs isn't expecting the y/n prompt and instead sends gdb=20 a sequence of commands '-inferior-tty-set /dev/pts/9', '-gdb-set height 0',= =20 etc. Each of these commands is interpreted by gdb as a response to the y/n= =20 prompt. Since the first letter isn't 'y' or 'n', gdb simply repeats the prompt for each of these commands. When the user tries to enter 'y'=20 emacs sends gdb the command '-interpreter-exec console "y"' (likewise for=20 'n'), making it impossible to answer the prompt. If emacs runs gdb=20 in a way that does not allow y/n prompts to be answered it should probably disable gdb's interactive-mode. However running gud-gdb with the same coredumpctl command worked for me. The prompt only prints once and y/n inputs are received correctly. If you want to skip this prompt you could also add 'set debuginfod enabled on/off' to your .gdbinit file or include it as a command line argument with -iex. --=20 You are receiving this mail because: You are on the CC list for the bug.=