From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-2.mimecast.com [207.211.31.81]) by sourceware.org (Postfix) with ESMTP id 3DD623858D32 for ; Sat, 2 May 2020 23:57:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3DD623858D32 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-143-ey1kQ38tNw-n2VzpgUz77g-1; Sat, 02 May 2020 19:57:18 -0400 X-MC-Unique: ey1kQ38tNw-n2VzpgUz77g-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0D7C7107ACCA; Sat, 2 May 2020 23:57:17 +0000 (UTC) Received: from f31-4.lan (ovpn-112-106.phx2.redhat.com [10.3.112.106]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9D55560612; Sat, 2 May 2020 23:57:16 +0000 (UTC) Date: Sat, 2 May 2020 16:57:15 -0700 From: Kevin Buettner To: gdb-patches@sourceware.org Subject: Re: [PUSHED/OBVIOUS] Remove gdb-gdb.gdb breakpoint on disappeared function info_command. Message-ID: <20200502165715.506efd68@f31-4.lan> In-Reply-To: <6dd0b78d43594ff851005a389e4a1579df546c51.camel@skynet.be> References: <20200501145451.20119-1-philippe.waroquiers@skynet.be> <20200501210229.5cb3950d@f31-4.lan> <6dd0b78d43594ff851005a389e4a1579df546c51.camel@skynet.be> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-9.5 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 May 2020 23:57:21 -0000 On Sun, 03 May 2020 01:01:26 +0200 Philippe Waroquiers wrote: > On Sat, 2020-05-02 at 22:19 +0100, Maciej W. Rozycki wrote: > > > Its use was quite obvious to anyone who actually debugged GDB from time > > to time: it was there so that you could break from the debuggee GDB into > > the debugger GDB with the use of the `info' command (with no arguments), > > as obviously using signals like SIGINT for that was quite problematic. I > > used to use this feature regularly, up until the last time a couple months > > back when I switched to non-GDB work. > I do limited GDB debugging, but was not aware of this feature. > I am not sure to understand the problem: > C-c works for me to interrupt GDB, and the top GDB gets > back the control (I typically launch top-gdb separately > and attach to the inferior GDB). FWIW, I also use Ctrl-C do get back to the top GDB. I'd also like to understand the use case when this is problematic. Kevin