From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id INMFEq/H2GehVRMAWB0awg (envelope-from ) for ; Mon, 17 Mar 2025 21:09:03 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=AIiu+b9u; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 251B41E100; Mon, 17 Mar 2025 21:09:03 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-6.4 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=4.0.1 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 DA89B1E05C for ; Mon, 17 Mar 2025 21:09:01 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 76A0B385840B for ; Tue, 18 Mar 2025 01:09:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 76A0B385840B Authentication-Results: sourceware.org; dkim=pass (1024-bit key, unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=AIiu+b9u Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTP id 427453858428 for ; Tue, 18 Mar 2025 01:07:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 427453858428 Authentication-Results: sourceware.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 427453858428 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.133.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1742260032; cv=none; b=nbw//dyLkyw9i48mk3vOg5MzhasguQoZbrkABB61dYFjpdy5l1v6C+CzF4oKPz5vRJHfX9jZisfd7XAXGo8xY4TQM/ALFFZF1c+d5e830wUOv/lbDDMaWpi/FMelp7b61jFFtcI/ZxQxskhTgFJmLpB7e+YnhpgXtkAACLOTFEI= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1742260032; c=relaxed/simple; bh=l0z7t3NB5I4RJ21/q2YiWt3lVqYrmnBetgIVpAx2kR8=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=LdMPs8O/FZeQh17bPSuHWUprosb+iomLbpxRP07lX6V6JnsoSR2KHAAU9wKxSgZjMzQvEOm171VQxB3gflnWRl3Iz36d+N2cWmcJInm4c5SS/cAM6T3OjEuiO7PmFShdQlGIPRKkYfbggABODpzCbyOi87YRw1hkqLZEuOCp0+0= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 427453858428 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1742260032; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=RSkTlpSGEl99Pgy0VROL7t3bKWiems2Tn0R6FgahuII=; b=AIiu+b9uw8wcY2wklTFY/mtKe5DxumyUMV7VehbOc3lgz6p/N42Djhgsf4a3LvNlskuXhW EX0crLdPBaOAZlc+yyZaL1WW1u9qTbMvK8kUE5b/Stfj8r887qWIWLs8KH4EvuB9yxGvfk RDKnnx1gYWpba5A9fx0gYndHgYpVVXA= Received: from mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-298-hOGky834MAmgr4pss8NMdA-1; Mon, 17 Mar 2025 21:07:10 -0400 X-MC-Unique: hOGky834MAmgr4pss8NMdA-1 X-Mimecast-MFC-AGG-ID: hOGky834MAmgr4pss8NMdA_1742260029 Received: from mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.12]) (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 mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id AAB921955DCD for ; Tue, 18 Mar 2025 01:07:09 +0000 (UTC) Received: from f41-zbm-amd (unknown [10.22.88.7]) by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id AD1D819541A6; Tue, 18 Mar 2025 01:07:08 +0000 (UTC) Date: Mon, 17 Mar 2025 18:07:01 -0700 From: Kevin Buettner To: Guinevere Larsen Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] gdb: Introduce user-friendly namespace identifier for "info shared" Message-ID: <20250317180701.2b570ecf@f41-zbm-amd> In-Reply-To: References: <20250313170004.3362207-2-guinevere@redhat.com> <20250314195108.2c4891a9@f41-zbm-amd> <20250314201112.29c30ab8@f41-zbm-amd> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.12 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: bMTGUSjOsDtB62IBGVe8M9NpQJTShLWcFMdZsxe9uAE_1742260029 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII 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 Mon, 17 Mar 2025 08:55:25 -0300 Guinevere Larsen wrote: > > My opinion is that we should suppress the NS column when there's > > only one linker namespace. > > I can give this a shot, but in my head there are 2 ways of implementing it: > > 1. If there is more than one linker namespace *active* when the command > is run; > 2. If there is more than one linker namespace *registered* when the > command is run; > > The main difference is: if the inferior has opened an SO in a namespace, > but has since closed it and everything loaded is in the default > namespace, should we still have the NS column? The first is closer to a > future plan of having an "active namespaces" convenience variable, while > the second is brand new code that I don't expect to use anywhere else, > but I can see an argument for it, so which do you prefer? I prefer option 1, in which the NS column is shown when there is more than one active namespace. Kevin