From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id eWEGG+Y7nmrk9jIAWB0awg (envelope-from ) for ; Mon, 07 Sep 2026 00:21:58 -0400 Authentication-Results: simark.ca; dkim=pass (2048-bit key; unprotected) header.d=linaro.org header.i=@linaro.org header.a=rsa-sha256 header.s=google header.b=aqA81sfj; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 66CC41E091; Mon, 07 Sep 2026 00:21:58 -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=unavailable 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 A29461E091 for ; Mon, 07 Sep 2026 00:21:56 -0400 (EDT) Received: from vm01.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id C77F34C31814 for ; Mon, 7 Sep 2026 04:21:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C77F34C31814 Authentication-Results: sourceware.org; dkim=pass (2048-bit key, unprotected) header.d=linaro.org header.i=@linaro.org header.a=rsa-sha256 header.s=google header.b=aqA81sfj Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) by sourceware.org (Postfix) with ESMTPS id 4B0AE4BC7ED0 for ; Mon, 7 Sep 2026 04:21:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 4B0AE4BC7ED0 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=linaro.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=linaro.org ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 4B0AE4BC7ED0 Authentication-Results: sourceware.org; arc=none smtp.remote-ip=2607:f8b0:4864:20::932 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1788754884; cv=none; b=AZ1Bd9L58GpEXPUmgEN/26qi0oT8NzYocG8Drh5xXt6Sun5NGwVOersKCfhRD9U3QwMFypADFx7W1cradu8dFurprfiagZWRJP7g3IWqpaeLav2PwJd5E4MBpbo45eO/b2gU0oq/48MkWvSJywc5b4zNRWRDIV44gcP7D6WPlP8= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1788754884; c=relaxed/simple; bh=5NghXjHylxFtt0uX6aQst12IJt3AGSpqWu7fkHo9GuA=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=GJAM+mXGERiU1gMHc2BbUiDO7+g2TUoYL3vS5g/OXGJoCje8VLRJdBXX38sSAdUz7VQe/Y8vKIu1hEzg5GixFxZUkq8/i/5iIisIohxbKiyeyYTEujiitZZvaaRkeIdxmjIoTA04JugGkew7IwbNEtQ+fB0B0FWkR2ZPUyLskEg= ARC-Authentication-Results: i=1; sourceware.org; dkim=pass (2048-bit key, unprotected) header.d=linaro.org header.i=@linaro.org header.a=rsa-sha256 header.s=google header.b=aqA81sfj DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4B0AE4BC7ED0 Received: by mail-ua1-x932.google.com with SMTP id a1e0cc1a2514c-980c4f5c921so50224241.2 for ; Sun, 06 Sep 2026 21:21:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1788754884; x=1789359684; darn=sourceware.org; h=content-transfer-encoding:content-type:mime-version:message-id:date :user-agent:references:in-reply-to:subject:cc:to:from:from:to:cc :subject:date:message-id:reply-to:content-type; bh=rzSsJu/Lj0O9G3nVXWikdgUNzK7TshwOpwlm6pmerkY=; b=aqA81sfju5QPCAMgyI6YKFgGQyseFgRJFgljM0VQWfKlnxijZyFyaMd/Q+AvAw/hin vRBIYR1CoIEelrFfkOo06jLzsLZyCJfwLzZSgX5XgNiYclF3q8pEqDA24bCUvlAJ+NKo f0/A6wseNzF251pdhxmh411jJpWyQ2lgkGrVjz/e32GDyXSU0mVCIMrIvi1a3xUrUnsn 1nLY5vAhC7So9v70ubJGIH/blGXS+DFAeuYtIMocl5LoBMIcCEVNw1QCjcoFSc93UULj mYUW0TylC3fAGpkmvBN90xnsg+/bA+YbV9Ux0IA+PLWUfTQ49WIF/1ASm7tR6zjKuoZo +I0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1788754884; x=1789359684; h=content-transfer-encoding:content-type:mime-version:message-id:date :user-agent:references:in-reply-to:subject:cc:to:from:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=rzSsJu/Lj0O9G3nVXWikdgUNzK7TshwOpwlm6pmerkY=; b=Dyk7KKxaMZOR2HNR4+zvyDieSPPjneNay5MQm5gyscvEr76pzk1QMT/3a2xYNq5mUd 4VX73dD2TtLdxR17Krg89h2evClJp6M3r3I0XxrAZFoQVOvzyUvS98IAuow/MLVETd+5 45+vCvPOfon7a75brRzpPJB62qhQ7tU0DFtUvyaDjY+BLAtiEug1Th7HxNDrxmX55K2X UhA2kkDOyK4R2Qkro1Z3UKVNJCUHtWS9oZEJQD1kQ0HoUrJXM2Ez/qMstSEHiqo3IZfj 1NHZBAHc9I7w+nmmmL4VZaY3+oK7ppdicLGYSPWRuNudqFUvsfatepZCo+h8Gr/Ej/Pu kOXA== X-Forwarded-Encrypted: i=1; AKwUvBwDXwYM0CaD63Dy/fzf01rUU+r6OOfiQXkk6LfULYzcNoiTMouPRtKt4sqsBTsOcAFvyU9eKMRg/OTWgg==@sourceware.org X-Gm-Message-State: AFuF++n0rrHZxQgPN7HfuWLF2UQ8ePKedOdQOZauF5Y/U4tkWzJBxU0l Pqt+3F3tfG2B+nUdjfogbQfy9K7akoDNd/dOEcl8vrcJKHJhxThrMJZZ64NelCyYwf32aXTEQjP ERsbS X-Gm-Gg: AYBFou1ILlm612MoQ2iiLPUfGpIyWAFu3IeXbiJIM+MSuRbbvF8Z9xb4qlAHR8fqCo5 6PxD/qk1J1g/1sUUbwnhA6OD4owO3jBexQpeUBct7ptAlMQyk1KvOEdXJQEv1Ayrg2OcD2/jdcC 861OHSCLTaKmoKdLQXLcugUdy5RC9F7R+AMLf2gFGTVOHf2KrHsu4L0yuMADZZf8M8WCmMOqRBS c+tTMPRdzvZzztqURqf9vKJ9Y1Sbx6NxKnKUvypd53vC1AZpFQnVWsZgqUjz9X7afJcNCMfdm92 0O9dqSwSZGUHqusQLXZmuxXylSa5Xp/RswEy/Eu6/QPI3k7ExuYHWYVtwc2Ov9A8//6fBwz+dAq fbsMk+CBqsheOyn3qAuSEmMH1quHRGVlmtsCE0X7IT+JMyY9U7TNWkGzfUIINFAt7n9JElHofG/ NifBWKZhXGAX+C3poEkNVVj9c7hPbImAOLtdKT/R6AMcbysaYVBB8rK8GhngMvdNr1uIrubfg1b KQJkzO/8g== X-Received: by 2002:a05:6102:2ac4:b0:778:30ee:f44b with SMTP id ada2fe7eead31-78a4ab31a99mr6156584137.13.1788754883616; Sun, 06 Sep 2026 21:21:23 -0700 (PDT) Received: from localhost ([2804:14d:7e39:8083:f04c:42e3:5943:38f6]) by smtp.gmail.com with ESMTPSA id ada2fe7eead31-78a47ae301fsm6199925137.7.2026.09.06.21.21.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 06 Sep 2026 21:21:23 -0700 (PDT) From: Thiago Jung Bauermann To: Simon Marchi Cc: Tom de Vries , gdb-patches@sourceware.org Subject: Re: [PATCH] gdb.gdb/python-helper.exp: Increase timeout values In-Reply-To: <26f8c856-5194-4fec-9314-fbd30473f493@simark.ca> (Simon Marchi's message of "Sun, 6 Sep 2026 21:02:49 -0400") References: <20260906040140.158197-1-thiago.bauermann@linaro.org> <87bjaannoi.fsf@linaro.org> <26f8c856-5194-4fec-9314-fbd30473f493@simark.ca> User-Agent: mu4e 1.14.3; emacs 30.2 Date: Mon, 07 Sep 2026 04:21:20 +0000 Message-ID: <875x0hofnj.fsf@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 Simon Marchi writes: > On 2026-09-06 16:13, Thiago Jung Bauermann wrote: >> And from Simon's email: >>=20 >>> Out of curiosity, is this with GDB build at -O0 or -O2 (or something >>> else)? With ASan or other instrumentation? >>> >>> I am asking because if it's -O2, then it's representative of what a user >>> would have in their hands. If some commands take a minute to run, then >>> we could at least check if it's because GDB is doing something terribly >>> inefficient. >>=20 >> Your responses made me realise I may be the only one seeing these >> timeouts, even if it's accross three machines. I found out that this is >> because I compile my test builds with -D_GLIBCXX_DEBUG. I hadn't >> realized until now that its impact on GDB performance was so big: >>=20 =E2=8B=AE >> With -D_GLIBCXX_DEBUG on the slower aarch64 server: >>=20 >> $ ./gdb -D data-directory -nx -q -ex 'maint set per-command time' -ex 'f= ile gdb' -ex quit >> Reading symbols from gdb... >> Time for "minsym install worker": wall 0.334, user 0.245, sys 0.011, use= r+sys 0.256, 76.6 % CPU >> Time for "minsym install worker": wall 0.336, user 0.242, sys 0.012, use= r+sys 0.254, 75.6 % CPU >> Time for "minsym install worker": wall 0.342, user 0.249, sys 0.008, use= r+sys 0.257, 75.1 % CPU >> Time for "minsym install worker": wall 0.349, user 0.231, sys 0.015, use= r+sys 0.246, 70.5 % CPU >> Time for "minsym install worker": wall 0.352, user 0.231, sys 0.019, use= r+sys 0.250, 71.0 % CPU >> Time for "minsym install worker": wall 0.356, user 0.237, sys 0.012, use= r+sys 0.249, 69.9 % CPU >> Time for "minsym install worker": wall 0.362, user 0.250, sys 0.009, use= r+sys 0.259, 71.5 % CPU >> Time for "minsym install worker": wall 0.362, user 0.240, sys 0.017, use= r+sys 0.257, 71.0 % CPU >> warning: File "/home/thiago.bauermann/src/binutils-gdb-wt/gdb/gdb-gdb= .gdb" auto-loading has been declined by your `auto-load safe-path' set to "= $debugdir:$datadir/auto-load". >> To enable execution of this file add >> add-auto-load-safe-path /home/thiago.bauermann/src/binutils-gdb-= wt/gdb/gdb-gdb.gdb >> line to your configuration file "/home/thiago.bauermann/.gdbinit". >> To completely disable this security protection add >> set auto-load safe-path / >> line to your configuration file "/home/thiago.bauermann/.gdbinit". >> For more information about this security protection see the >> "Auto-loading safe path" section in the GDB manual. E.g., run from the = shell: >> info "(gdb)Auto-loading safe path" >> warning: File "/home/thiago.bauermann/src/binutils-gdb-wt/gdb/gdb-gdb= .py" auto-loading has been declined by your `auto-load safe-path' set to "$= debugdir:$datadir/auto-load". >> Time for "DWARF indexing worker": wall 3.786, user 2.786, sys 0.847, use= r+sys 3.633, 96.0 % CPU >> Time for "DWARF indexing worker": wall 3.786, user 2.711, sys 0.954, use= r+sys 3.665, 96.8 % CPU >> Time for "DWARF indexing worker": wall 3.786, user 2.741, sys 0.933, use= r+sys 3.674, 97.0 % CPU >> Time for "DWARF indexing worker": wall 3.787, user 2.822, sys 0.872, use= r+sys 3.694, 97.5 % CPU >> Time for "DWARF indexing worker": wall 3.791, user 2.688, sys 0.979, use= r+sys 3.667, 96.7 % CPU >> Time for "DWARF indexing worker": wall 3.791, user 2.771, sys 0.880, use= r+sys 3.651, 96.3 % CPU >> Time for "DWARF indexing worker": wall 3.792, user 2.936, sys 0.778, use= r+sys 3.714, 97.9 % CPU >> Time for "DWARF indexing worker": wall 3.793, user 2.762, sys 0.905, use= r+sys 3.667, 96.7 % CPU >> Time for "DWARF skeletonless type units": wall 0.006, user 0.005, sys 0.= 000, user+sys 0.005, 83.3 % CPU >> Time for "DWARF add parent map": wall 0.116, user 0.114, sys 0.001, user= +sys 0.115, 99.1 % CPU >> Time for "DWARF finalize worker": wall 15.504, user 10.265, sys 4.293, u= ser+sys 14.558, 93.9 % CPU >> Time for "DWARF finalize worker": wall 0.000, user 0.000, sys 0.000, use= r+sys 0.000, nan % CPU >> Time for "DWARF finalize worker": wall 15.770, user 10.372, sys 4.360, u= ser+sys 14.732, 93.4 % CPU >> Time for "DWARF finalize worker": wall 16.329, user 10.965, sys 4.415, u= ser+sys 15.380, 94.2 % CPU >> Time for "DWARF finalize worker": wall 68.077, user 33.268, sys 26.932, = user+sys 60.200, 88.4 % CPU >> Time for "DWARF finalize worker": wall 70.295, user 34.154, sys 27.911, = user+sys 62.065, 88.3 % CPU >> Time for "DWARF finalize worker": wall 73.817, user 37.446, sys 28.763, = user+sys 66.209, 89.7 % CPU >> Time for "DWARF finalize worker": wall 73.916, user 37.227, sys 28.555, = user+sys 65.782, 89.0 % CPU >> Time for "DWARF finalize worker": wall 74.662, user 37.951, sys 28.837, = user+sys 66.788, 89.5 % CPU > > And is this with or without compiler optimizations? I have the feeling > that C++ without optimizations (especially the standard lib) is slow, > because you have a ton of layers of functions that would normally get > optimized out, but are there in a -O0 build. Ah, sorry for ignoring that part of your question. I thought it wasn't relevant anymore given that I was indeed using instrumentation. I also build with -g -O0. Though now looking at the gcc manpage perhaps I should switch to -g -Og. >> Tom, sorry for sending you on a wild goose chase. >>=20 >> This patch is clearly not needed. > > If you have a particularly slow build, what you can do is use a local > timeout factor when testing: > > $ echo 'set gdb_test_timeout [expr 5 * $timeout]' >> testsuite/site.exp Thanks for the tip. I do that when I test on a setup that I expect to be extra slow. I just failed to noticed that that was the case this time. > On the other hand if the same single test often times out in a lot of > scenarios or for a lot of people, then it could make sense to increase > the timeout for that one in particular. There's one test setup which I use sometimes which may or may not qualify for this test. I'll mention it in my reply to Tom's patch=C2=B9. --=20 Thiago (he/him) =C2=B9 https://inbox.sourceware.org/gdb-patches/20260906154838.139837-1-tde= vries@suse.de/