From: Pedro Alves <pedro@palves.net>
To: John Baldwin <jhb@FreeBSD.org>, gdb@sourceware.org
Subject: Re: GDB BoF notes - GNU Cauldron 2023
Date: Fri, 29 Sep 2023 10:57:49 +0100 [thread overview]
Message-ID: <adddcf21-6214-79fd-8461-b464f292466b@palves.net> (raw)
In-Reply-To: <453315e3-2483-7a1d-6ecc-23adc7d24fd3@FreeBSD.org>
On 2023-09-27 21:27, John Baldwin wrote:
> +1 to both of these. One caveat about the pagination case is that I
> use custom commands that can sometimes generate a lot of output (e.g.
> walking linked-lists in a kernel crash image outputting info about
> each entry, or similar things for entries in descriptor rings). If one
> of these scripts has a bug that causes an infinite loop, the pager
> seems to be the only way to stop the command. In particular, Ctrl-C
> doesn't work in my experience to cancel a user command stuck in an
> infinite loop. It might be nice to ensure that Ctrl-C can cancel both
> user and builtin commands that are either stuck or generating reams of
> output.
>
I'm surprised to hear this, as it's already supposed to be possible to
Ctrl-C in those cases. But I won't be surprised if there's some bug
swallowing Ctrl-C somewhere. I do recall that Kevin fixed a good number
of them for the SIGTERM propagation patches. It may also be that it's the
user command that is buggy -- e.g., if it's a python command and then the
command swallows the keyboard interrupt exceptions.
next prev parent reply other threads:[~2023-09-29 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 12:41 Pedro Alves
2023-09-27 13:55 ` Simon Marchi
2023-09-27 14:00 ` Guinevere Larsen
2023-09-29 9:24 ` Lancelot SIX
2023-09-29 9:52 ` Turn history saving on by default? (Re: GDB BoF notes - GNU Cauldron 2023) Pedro Alves
2023-09-29 10:30 ` Guinevere Larsen
2023-09-27 20:27 ` GDB BoF notes - GNU Cauldron 2023 John Baldwin
2023-09-29 9:57 ` Pedro Alves [this message]
2023-10-06 21:35 ` John Baldwin
2023-09-28 20:44 ` Tom Tromey
2023-09-29 4:48 ` Sam James
2023-09-29 10:25 ` Pedro Alves
2023-10-05 7:08 ` Tom de Vries
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=adddcf21-6214-79fd-8461-b464f292466b@palves.net \
--to=pedro@palves.net \
--cc=gdb@sourceware.org \
--cc=jhb@FreeBSD.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).