From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 84T3J4lAcmMnUBgAWB0awg (envelope-from ) for ; Mon, 14 Nov 2022 08:20:09 -0500 Received: by simark.ca (Postfix, from userid 112) id 96D591E124; Mon, 14 Nov 2022 08:20:09 -0500 (EST) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=wjjI9n/Z; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_MED,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 1BE921E0CB for ; Mon, 14 Nov 2022 08:20:09 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 9D0E73858428 for ; Mon, 14 Nov 2022 13:20:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9D0E73858428 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1668432008; bh=WSGTrFRgRt1V0acdIcGMuRCcG46KkMb2CSYGaNw5YcQ=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=wjjI9n/ZNdEQrPadmzIpKPXAN7hr4rCBvyCJohRFVlEVtYyxxc2TuMFqwLXHAOR33 SlUZRzrmsJv6aN2AM8V2uNNGwZUlQ8gVYi7uL5egOjikdnaSZV3y2ihNpGS9ibKU7A phjAH6tx1fRfW2i7eDxRQjXqV8WBIEfyJ61C40ak= Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id 3E20B3858D32 for ; Mon, 14 Nov 2022 13:19:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3E20B3858D32 Received: from [10.0.0.11] (unknown [217.28.27.60]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 6BCAD1E0CB; Mon, 14 Nov 2022 08:19:46 -0500 (EST) Message-ID: <0a9685a1-805b-2212-9464-e5278ec05279@simark.ca> Date: Mon, 14 Nov 2022 08:19:45 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [PATCH v2] gdb: make "start" breakpoint inferior-specific Content-Language: en-US To: Tom de Vries , Simon Marchi , gdb-patches@sourceware.org References: <691c5a58-68ae-5fe9-2f3d-34fb7af69ad0@palves.net> <20221108212008.1792090-1-simon.marchi@efficios.com> <1c02e882-c19e-483e-e50c-634fbe282988@suse.de> <4c7b3e65-08a6-913a-8e0f-8d3812bbd005@efficios.com> <5d4c4f03-4aa5-cf36-cb4d-cf8293f247a1@suse.de> <2c61909c-f5d9-2a69-bbd0-a05a0c39f5f0@suse.de> In-Reply-To: <2c61909c-f5d9-2a69-bbd0-a05a0c39f5f0@suse.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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: , From: Simon Marchi via Gdb-patches Reply-To: Simon Marchi Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 11/14/22 06:29, Tom de Vries wrote: > On 11/11/22 20:03, Simon Marchi via Gdb-patches wrote: >>> I'm not sure if this is a better solution: it's more intrusive. >> Ah, that would be good too.  We wouldn't have to bake in the knowledge >> of which languages use which operator.  But I'm also a bit scared of >> other unintended consequences when looking up the main symbol, as I see >> the current_language is involved in some places.  To be safe, I'll just >> go with my naive patch.  Thanks for the suggestion. > > FWIW, I've just stumbled onto language unknown, and realized that strictly speaking we've got a regression because we used to have: > ... > $ gdb -q -batch a.out -ex "set language unknown" -ex start > Temporary breakpoint 1 at 0x40050b: file /home/vries/hello.c, line 6. > > Temporary breakpoint 1, main () at /home/vries/hello.c:6 > 6         printf ("hello\n"); > Warning: the current language does not match this frame. > $ > ... > but now we have: > ... > $ gdb -q -batch a.out -ex "set language unknown" -ex start > expression parsing not implemented for language "Unknown" > $ > ... > > I don't really care about this, I thought I just mention it. Huh... What is "set language unknown" useful for, generally speaking? If debugging something in a language GDB doesn't know about, I think it will fall back to minimal. Could we just not expose the "unknown" language to the user? Simon