From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-f54.google.com (mail-wm1-f54.google.com [209.85.128.54]) by sourceware.org (Postfix) with ESMTPS id E13483858C78 for ; Fri, 29 Sep 2023 09:57:52 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E13483858C78 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=palves.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wm1-f54.google.com with SMTP id 5b1f17b1804b1-406402933edso55730155e9.2 for ; Fri, 29 Sep 2023 02:57:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695981472; x=1696586272; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=EsuDUvW385Uru/JxuRViavUhE803H1XPF5tuu5NoTVY=; b=HYwZ50VJmHGLOtL2Rn8kSrMs3/n4O3xm2pLiFoWjeQsSibL8bmmcEx0IA8qGQy6PXz Fz/OYEZ1HOKzva7yyQmGHw+WK5VTZ3zyO6k/sk8ktAK48w53+IklpsHAn+/crBsoLsm6 I7JXom7nN4JeREkIAtr1dWmfLVPJhowvlJx+rh9S2+8/VG/7lYIokJHwlNd5+P3/aiSb bVIXLAJXiYcyrMH4onLQDUQ5/1lsLF9kOykn9CvFS0+Xr5ejU12JCP10s3O1Ir+uTThm biN3fA6rlIP/G1VB/oqyLGrlAaAuEy88wAYaNyxdbodTrCv7DiufPgg2bH6XZbeHRuZb SHLg== X-Gm-Message-State: AOJu0YzdzzjNdGt8LhqBv09yY37ZumtjEEhZbRMpKBlq0VRySioOhhYE fdAPw3I0bR5YHqbIa3xiQRAhaZXbE/tzrA== X-Google-Smtp-Source: AGHT+IFbmLjsWOg0twlS/vyVifUPBbB2WdfYLJ5vbBgs8PylD4ylN2RsZVbYZD61G/tUFDX/mqBiQw== X-Received: by 2002:a7b:ca53:0:b0:405:3b1f:968b with SMTP id m19-20020a7bca53000000b004053b1f968bmr3428200wml.21.1695981471569; Fri, 29 Sep 2023 02:57:51 -0700 (PDT) Received: from ?IPV6:2001:8a0:f939:d200:bc52:8881:959:d6ef? ([2001:8a0:f939:d200:bc52:8881:959:d6ef]) by smtp.gmail.com with ESMTPSA id y21-20020a7bcd95000000b00405c7591b09sm1069227wmj.35.2023.09.29.02.57.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 29 Sep 2023 02:57:51 -0700 (PDT) Message-ID: Date: Fri, 29 Sep 2023 10:57:49 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: GDB BoF notes - GNU Cauldron 2023 Content-Language: en-US To: John Baldwin , gdb@sourceware.org References: <1e26c71e-e242-de11-a687-46e05586e608@palves.net> <453315e3-2483-7a1d-6ecc-23adc7d24fd3@FreeBSD.org> From: Pedro Alves In-Reply-To: <453315e3-2483-7a1d-6ecc-23adc7d24fd3@FreeBSD.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-5.8 required=5.0 tests=BAYES_00,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,KAM_DMARC_STATUS,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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.