From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id /cC/KzbKxWcF2QMAWB0awg (envelope-from ) for ; Mon, 03 Mar 2025 10:26:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1741015606; bh=7IRZu5mlqB3rDA+9NEGdMgaj6v6q2F7Vw8VtauZ7RyU=; h=Date:Subject:To:Cc:References:From:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=NjhRqONfN/H7JUjVPH8fz49DIjrUOfAQJ5QzAAPsIY2AEJbCQfVaT+txdCq2qre+T lAhTnIf2l1cyodRbufnyA6Z7k/kNg3Kt6YUhciZO0IFCWercdaI8YLOKSThvAKdtUR n0BiH0FYe2ioEQBJR+fTdAuwXsvd95c2nCcfY9/4= Received: by simark.ca (Postfix, from userid 112) id A60081E105; Mon, 3 Mar 2025 10:26:46 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.4 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED autolearn=unavailable autolearn_force=no version=4.0.0 Authentication-Results: simark.ca; dkim=pass (1024-bit key; unprotected) header.d=simark.ca header.i=@simark.ca header.a=rsa-sha256 header.s=mail header.b=sTWD8j7+; dkim=pass (1024-bit key) header.d=simark.ca header.i=@simark.ca header.a=rsa-sha256 header.s=mail header.b=wMLBWwdn; dkim-atps=neutral Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 4C7341E05C for ; Mon, 3 Mar 2025 10:26:46 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id EF1F63858D29 for ; Mon, 3 Mar 2025 15:26:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EF1F63858D29 Authentication-Results: sourceware.org; dkim=pass (1024-bit key, unprotected) header.d=simark.ca header.i=@simark.ca header.a=rsa-sha256 header.s=mail header.b=sTWD8j7+; dkim=pass (1024-bit key) header.d=simark.ca header.i=@simark.ca header.a=rsa-sha256 header.s=mail header.b=wMLBWwdn Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id 884533858D21 for ; Mon, 3 Mar 2025 15:26:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 884533858D21 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=simark.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark.ca ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 884533858D21 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=158.69.221.121 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1741015575; cv=none; b=H0r8Vz2JQnE5PV1OiDAVJ74yovkuYprDL44U/RhhnbApZC8Ng28hR5FaAOIk9AYAOF9ZONmDAdPAfKANzGPQWv5QWCiQ39eRJZ3OnYYbFKF3hZuSnOjTfbSOE1WpJ7UQB08qQxghqmiHeE79iE6onefe+K074U4FNZQ+z3QvWSQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1741015575; c=relaxed/simple; bh=7IRZu5mlqB3rDA+9NEGdMgaj6v6q2F7Vw8VtauZ7RyU=; h=DKIM-Signature:DKIM-Signature:Message-ID:Date:MIME-Version: Subject:To:From; b=XJEI2HCSMF2heC8lFh2/5JiNJ6IT/OVFSdOqzMVEd/1u4QQN8w88ck9eGMJZCuR1LN/yJecYhjwaK795ssNIk+kTpKt6i+bDuNTt7y6iZqaogAXfgNiWwVKC7RJEC+bh8qH1wteLVNv1PB45qmRO7lMNIExPGkZgNyZwpMa+xbA= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 884533858D21 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1741015575; bh=7IRZu5mlqB3rDA+9NEGdMgaj6v6q2F7Vw8VtauZ7RyU=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=sTWD8j7+gjVvlHGiUjOtxCA+rMdy8wX8350dBnv7IADiTLV8BVRDI4WyurRFTtlZ7 IWhrrtBHkkdSa81CxjyDOwwDUYe7pQLZh7bGAdLS/UAhkJo//kuSTf+09U3k8lVLrY /XQdiPCihkSL1+do2TXbMnvcSQk3FygMaamiyDEA= Received: by simark.ca (Postfix, from userid 112) id 3A7E21E10A; Mon, 3 Mar 2025 10:26:15 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1741015574; bh=7IRZu5mlqB3rDA+9NEGdMgaj6v6q2F7Vw8VtauZ7RyU=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=wMLBWwdnAjQ6LpTfxFJ6U2RjQPN9XJtitqAp8zpajY0E4kPDnsW2YLn5vcscXCogz ixP2unRkpVFF6KDpoplgI5bdE9mMSSC9pYjK/e191lhC8dZ2f89fIho+YG+agq1TiV WC7zHnPXZIV9SfmYtbAhX1LT22YMvHzjAemBgitw= Received: from [172.16.0.192] (96-127-217-162.qc.cable.ebox.net [96.127.217.162]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 19D491E05C; Mon, 3 Mar 2025 10:26:14 -0500 (EST) Message-ID: <6adc8d6d-eb2c-41b5-af60-ee3191720ee2@simark.ca> Date: Mon, 3 Mar 2025 10:26:13 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] gdb: add load-libthread-db-quietly option To: Gregory Heytings Cc: Eli Zaretskii , gdb-patches@sourceware.org References: <865xktq8gw.fsf@gnu.org> <8634fwq1sr.fsf@gnu.org> <9ab7816e-716b-432d-ac69-8c311ce2f38c@simark.ca> <121e13947648576b7158@heytings.org> Content-Language: fr From: Simon Marchi In-Reply-To: <121e13947648576b7158@heytings.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces~public-inbox=simark.ca@sourceware.org On 3/3/25 10:04 AM, Gregory Heytings wrote: > >> >> People ask us to make it possible to turn this or that message on and off all the time. The proposed command, "set load-libthread-db-quietly", is very specific to that use case. >> > > Indeed. > >> >> Could we add perhaps a prefix command (or find an existing appropriate one) that would allow us to easily add more such knobs? I'm thinking of something like (maybe not a good name, but just for the example): >> >> (gdb) set message load-libthread-db on/off >> > > Would > > set print load-libthread-db on/off > > be better? > I initially thought it wouldn't be a good idea because I thought that "set/show print" only contained options regarding the "print" command, which is not the same thing as printing or not printing messages. But it is used for tweaking messages already. I see: set print symbol-loading -- Set printing of symbol loading messages. set print thread-events -- Set printing of thread events (such as thread start and exit). set print inferior-events -- Set printing of inferior events (such as inferior start and exit). So, unless there is a better place for this type of commands that I don't know about, I think "set print" would be fine. Simon