From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id DPowAPIS+mlX+BYAWB0awg (envelope-from ) for ; Tue, 05 May 2026 11:55:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1777996529; bh=HGJQgEfjoEF4tBJgF5xeQigMxr8hVsOk3czpahoBIUI=; h=Date:Subject:To:Cc:References:From:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=E3olL9hLcQJpIbfvVb7p+JwHwCQwMFitBVSu7v1I4cAh3vGBYS1D9U9segzjtLQUx OF8ReEQfCwOOmzM/ROK/KYezREI5K1xd300lXxlXvIJ8DJVqi06KGNZCnTlwtTrQVc GHiToUPeRMr47VXP6XQRTTFc5AuN0RdcTW31zxvE= Received: by simark.ca (Postfix, from userid 112) id E42811E0BA; Tue, 05 May 2026 11:55:29 -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_VALIDITY_CERTIFIED_BLOCKED, RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED autolearn=ham autolearn_force=no version=4.0.1 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=w8NZegiq; dkim-atps=neutral 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 7971C1E067 for ; Tue, 05 May 2026 11:55:29 -0400 (EDT) Received: from vm01.sourceware.org (localhost [127.0.0.1]) by sourceware.org (Postfix) with ESMTP id 062074BA7989 for ; Tue, 5 May 2026 15:55:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 062074BA7989 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=w8NZegiq Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id 8C14B4BA2E15 for ; Tue, 5 May 2026 15:54:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8C14B4BA2E15 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 8C14B4BA2E15 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=1777996495; cv=none; b=w5hoQHm1R0PniCZn6yXqajp27HgdJT8MT6Do3Ch9As4LVDwuOhvRgDKjy1fThlLXcv2grl+fza6CaDE/+u4StSFocdDlm9figLcLyNvaPcufvMnjXdmKQh3wNje2QDQhE2yIH01IYQDGy4FAHjZkNX++dkglrC+ox5dDhdnlkHk= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1777996495; c=relaxed/simple; bh=HGJQgEfjoEF4tBJgF5xeQigMxr8hVsOk3czpahoBIUI=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=KY0Yl+XUgbAYHJuK9lgfXh2QhtsaiYZ43dgCoKRkTWQlvkELLvvhggBYCVjHrWnz4JcEnmPP/2IrYN7W8z3/cUeKl//T3PhvGWmuQnseIwe+cZJsEh5JCjMP3Pqgj+MSqAPhfrsQwYgIrI27cSqnYbdkJNTkeCc8z+tFH2ZRa9c= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8C14B4BA2E15 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1777996493; bh=HGJQgEfjoEF4tBJgF5xeQigMxr8hVsOk3czpahoBIUI=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=w8NZegiq/a/BUf6z6CWW9gzademP60ewHKvGYqUy/RpFnKivmWNXmn++xNPPB1/z3 tMTjwST9LCgladLZ4rKTyedohzUJUiGcCyw7vpmDZKpqzqOE+hTRa5hzzC9qFDx/XQ QrRshmSYzvU6N2LF4bIQcMoFTAlFUmyB24WRQqpc= Received: by simark.ca (Postfix) id 53C981E067; Tue, 05 May 2026 11:54:53 -0400 (EDT) Message-ID: Date: Tue, 5 May 2026 11:54:53 -0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] gdb, testsuite: increase timeout in gdb.threads/attach-non-stop.exp To: "Metzger, Markus T" Cc: "gdb-patches@sourceware.org" References: <20260504071636.1571615-1-markus.t.metzger@intel.com> <20260504071636.1571615-4-markus.t.metzger@intel.com> Content-Language: en-US From: Simon Marchi In-Reply-To: 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 2026-05-05 02:15, Metzger, Markus T wrote: > Hello Simon, > >> On 5/4/26 3:16 AM, Markus Metzger wrote: >>> Attaching sporadically timed out on my system while reading symbols... >>> >>> Reading symbols from .../attach-non-stop... >>> (gdb) gdb_do_cache: can_spawn_for_attach ( ) >>> builtin_spawn .../attach-non-stop >>> attach 729532 >>> Attaching to program: .../attach-non-stop, process 729532 >>> [New LWP 729574 (id 2)] >>> [New LWP 729573 (id 3)] >>> [New LWP 729572 (id 4)] >>> [New LWP 729571 (id 5)] >>> [New LWP 729570 (id 6)] >>> [New LWP 729569 (id 7)] >>> [New LWP 729568 (id 8)] >>> [New LWP 729567 (id 9)] >>> [New LWP 729566 (id 10)] >>> [New LWP 729565 (id 11)] >>> Reading symbols from /lib/x86_64-linux-gnu/libc.so.6... >>> FAIL: gdb.threads/attach-non-stop.exp: target-non-stop=off: non-stop=on: >> cmd=attach: attach (timeout) >>> >>> Adjust the timeout to avoid sporadic fails. >> >> Not saying it's necessarily a bad idea, but I'd like some more details >> on what is taking so long. From the above, I understand that GDB is >> reading debug info for libc, which is not that big in the grand scheme >> of things... >> >> I'd like to know "this step is taking about X seconds", just to make >> sure we don't paper over an actual problem. > > The issue happens sporadically, typically while running the entire test > suite (I use FORCE_PARALLEL). I tried reproducing it by just running this > one test but couldn't. > > I cannot say what takes so long and how long exactly it takes, but increasing > the timeout helped the test pass, so it wasn't actually hanging. One sporadic > fail less. If the timeout is mostly related to how you run the testsuite, then I think it would be more appropriate to set a local timeout factor. For instance, because I build GDB with -O0, with all kinds of checks that make it slower (_GLIBCXX_DEBUG, ASan), I also get some random timeouts that are not there when building normally, so I use: echo 'set gdb_test_timeout [expr 5 * $timeout]' >> testsuite/site.exp in my build directory. Simon