From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id sLRmKkUWnWc/dyAAWB0awg (envelope-from ) for ; Fri, 31 Jan 2025 13:28:21 -0500 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=GCZUxbSS; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id A8F991E105; Fri, 31 Jan 2025 13:28:21 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-7.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,RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=4.0.0 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 5A3F51E08E for ; Fri, 31 Jan 2025 13:28:21 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 262663857719 for ; Fri, 31 Jan 2025 18:28:21 +0000 (GMT) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTP id 6C45E3858429 for ; Fri, 31 Jan 2025 17:49:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 6C45E3858429 Authentication-Results: sourceware.org; dmarc=pass (p=none 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 6C45E3858429 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1738345748; cv=none; b=sF9FKnZFH8UHk4gc1bBdY3eajWOXJtJotrcau1FI/cwCzbNukvlFqWZCRac5k++Daq4sWenE95tsVuRd24ijhWsdGTZ1Dy9yj/UHNxI6NIE3Om/I49REHSCRAMUT7HKJ0Vh8rU0vjX1s8T+Rwsyo4/ufpqvqiA3eK40apfwPJhk= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1738345748; c=relaxed/simple; bh=ceGTg4kBoiyGGZ1C0TPhBmWX2t0Nx+7g6Nz7Ehjcvk0=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=J3OZjlV5mKGTLE4vBEGMO1Z/HjCeMJb4BTKUaDMPknJgCMwEZptW01ZjgVul4W7opvBzIqzDnn1gzUbegj+c0YVgFT2D6EgpHfHyYf/straF69ItsURrnU5qQMzcz1YPBpJXJmy/4H3DrdWf/FCYJG/dO8CjV3Q59YpfdS2CVAI= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6C45E3858429 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=GCZUxbSS DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1738345748; 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=vwbP0+08hwBPEhc6nDY/wr4jvWIOAgTJWI4IAMmoubQ=; b=GCZUxbSSwpfOeu30kF5VdkoCg9eBlGmg0971lqPGzoAKwzDm5q7fztWWN+d0HXhBL3HqTl +sy/L3iWBuI9oiqqF8uPF5vpWqkGIc4oFKOjXUz03+rjMgewm2bAuKb6mepayCPifdNflL clC7LJflcxySQMlAAvggmCLyUwK1kI0= Received: from mx-prod-mc-05.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-287-pwcQ4R_WPAq3TOMSPZ6IcA-1; Fri, 31 Jan 2025 12:49:06 -0500 X-MC-Unique: pwcQ4R_WPAq3TOMSPZ6IcA-1 X-Mimecast-MFC-AGG-ID: pwcQ4R_WPAq3TOMSPZ6IcA Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (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-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id EB1031956080; Fri, 31 Jan 2025 17:49:05 +0000 (UTC) Received: from f41-1.lan (unknown [10.22.64.223]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id E6E5B18008F0; Fri, 31 Jan 2025 17:49:04 +0000 (UTC) From: Kevin Buettner To: gdb-patches@sourceware.org Cc: tom@tromey.com, Kevin Buettner Subject: [PATCH v5 02/11] Allow TLS access to work in gdb.server/no-thread-db.exp Date: Fri, 31 Jan 2025 10:45:25 -0700 Message-ID: <20250131174747.921323-4-kevinb@redhat.com> In-Reply-To: <20250131174747.921323-2-kevinb@redhat.com> References: <20250131174747.921323-2-kevinb@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: q1pYgONBb1LU0j9qkOLtZP85PNksYrdfh7QGgjZKCxo_1738345746 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit content-type: text/plain; charset="US-ASCII"; x-default=true 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 The patches later in the series add GDB-internal TLS support for certain targets. This commit updates the "print foo" test in gdb.server/no-thread-db.exp to accept either a TLS failure (when libthread_db isn't available) or printing the correct answer, which will occur when GDB's internal TLS address resolution can be used. I'm making this change prior to the commits which actually add the GDB-internal TLS support in order to avoid tripping regression testers. --- gdb/testsuite/gdb.server/no-thread-db.exp | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/gdb/testsuite/gdb.server/no-thread-db.exp b/gdb/testsuite/gdb.server/no-thread-db.exp index 656fad1a560..baad81b0f8e 100644 --- a/gdb/testsuite/gdb.server/no-thread-db.exp +++ b/gdb/testsuite/gdb.server/no-thread-db.exp @@ -57,6 +57,8 @@ gdb_breakpoint ${srcfile}:[gdb_get_line_number "after tls assignment"] gdb_continue_to_breakpoint "after tls assignment" # Printing a tls variable should fail gracefully without a libthread_db. +# Alternately, the correct answer might be printed due GDB's internal +# TLS support for some targets. set re_exec "\[^\r\n\]*[file tail $binfile]" gdb_test "print foo" \ - "Cannot find thread-local storage for Thread \[^,\]+, executable file $re_exec:\[\r\n\]+Remote target failed to process qGetTLSAddr request" + "= 1|(?:Cannot find thread-local storage for Thread \[^,\]+, executable file $re_exec:\[\r\n\]+Remote target failed to process qGetTLSAddr request)" -- 2.48.0