From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id vaSEFKP98WkrWQMAWB0awg (envelope-from ) for ; Wed, 29 Apr 2026 08:46:27 -0400 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=rGQH1Rro; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 2D4491E0BA; Wed, 29 Apr 2026 08:46:27 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.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,RCVD_IN_MSPIKE_H2,RCVD_IN_VALIDITY_CERTIFIED_BLOCKED, RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED autolearn=ham autolearn_force=no version=4.0.1 Received: from vm01.sourceware.org (vm01.sourceware.org [38.145.34.32]) (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 508361E067 for ; Wed, 29 Apr 2026 08:46:26 -0400 (EDT) Received: from vm01.sourceware.org (localhost [127.0.0.1]) by sourceware.org (Postfix) with ESMTP id E24494BA7982 for ; Wed, 29 Apr 2026 12:46:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E24494BA7982 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1777466784; bh=lHt90SpDLn9DlsLrGWflixx5Yhgw5iXXz6XvC4zXZOg=; h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=rGQH1RroCW9cNAyIx41+97w2vuOakN93JauSM+hvmF2vQSpyaTofBr5GbVV66f5ac Phvm2R/5/kPTxrUMd7DzxADcQlDXMRQi2rTkXnHzC2I0xDd838Ftp/LY4Jtt+q7AGB NtAA78U5K1bR39UDf5PgLabfhIBsB2jw/Z2eueSs= Received: from mail-4320.protonmail.ch (mail-4320.protonmail.ch [185.70.43.20]) by sourceware.org (Postfix) with ESMTPS id BA0814BB1C02 for ; Wed, 29 Apr 2026 12:45:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org BA0814BB1C02 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org BA0814BB1C02 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1777466753; cv=none; b=GRmsvXeL8/wcx5yWs0UFWRBuzoud/J+OhTUWpR2+x9HcBUn3/BN2zkCc3E4s3DLT3JSPA75QtkJ37T4AC6AKPB33DFKWvpTFkvEfsUOTvOR0QD7wDz5nrz+aksGKLnKxgC3bk8NIe5LGnq5EGvoldoXRW2UT+bw/OcKXGWJffXM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1777466753; c=relaxed/simple; bh=b1f3CY/VVAeDlTead30u1xttBRcwygD3SI5StUeayG4=; h=DKIM-Signature:Date:To:From:Subject:Message-ID:MIME-Version; b=mEBhlt3OdlxUGa+HN1UIeN8zHIZJERkRM2B8oSU2NNjilqWZsF0QKiDgw5cmi3bsfmckN/fjrHltnd3rqq6J3P/aLECyCeYU1xJ4wia9yafbNJ4vTlhhyfQmf8EC9dGfq1KQa1rf3+MZXoT50Zy3XjscCoF8D8X/XOlwwSOyqes= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BA0814BB1C02 Date: Wed, 29 Apr 2026 12:45:42 +0000 To: "gdb@sourceware.org" Subject: Question about adding a new option vs extending an existing one Message-ID: Feedback-ID: 10509189:user:proton X-Pm-Message-ID: fe0717f588e903a3f30a1768c067fb7b6ce985c6 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Zander Work via Gdb Reply-To: Zander Work Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" Hello, I'm interested in writing a patch for GDB which allows a user to change the= radix used for displaying function offsets in instruction listings (exampl= e below), right now it only uses decimal, and doesn't respect the existing = radix settings (either `radix` or `output-radix`). I want to contribute a patch that allows the user to change the radix used = for displaying these offsets, but I'm not sure if it would be best to re-us= e the value of `output-radix`, or to define a new setting (eg, `offset-radi= x` maybe). Additionally, if a new option should be added, would it be appropriate to h= ave `set radix` also set that new one (I would assume yes). Does anyone have any opinions on this? My personal feeling is that reusing = `output-radix` would be best. --- (gdb) set radix 16 Input and output radices now set to decimal 16, hex 10, octal 20. (gdb) x/8i $rip =3D> 0x7ffff7fe0c00 <_start>: mov %rsp,%rdi 0x7ffff7fe0c03 <_start+3>: call 0x7ffff7fe1750 <_dl_start> 0x7ffff7fe0c08 <_dl_start_user>: mov %rax,%r12 0x7ffff7fe0c0b <_dl_start_user+3>: mov %rsp,%r13 0x7ffff7fe0c0e <_dl_start_user+6>: mov 0x1cb9c(%rip),%edx # = 0x7ffff7ffd7b0 <_rtld_global+1968> 0x7ffff7fe0c14 <_dl_start_user+12>: test $0x2,%edx 0x7ffff7fe0c1a <_dl_start_user+18>: je 0x7ffff7fe0c2d <_dl_start_us= er+37> 0x7ffff7fe0c1c <_dl_start_user+20>: mov $0x1,%esi ^^ i am referring to these offsets