Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb, testsuite: increase timeout in gdb.threads/attach-non-stop.exp
Date: Tue, 5 May 2026 11:54:53 -0400	[thread overview]
Message-ID: <eb205100-f1ac-4f5f-8c5e-1b4c666735f5@simark.ca> (raw)
In-Reply-To: <DM8PR11MB57492D6827E7470C90EC4CA2DE3E2@DM8PR11MB5749.namprd11.prod.outlook.com>



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

  reply	other threads:[~2026-05-05 15:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04  7:16 [PATCH] gdb, btrace: fix wrong #endif comments Markus Metzger
2026-05-04  7:16 ` [PATCH] gdb: fix an issue with thread list corruption Markus Metzger
2026-05-04 15:30   ` Simon Marchi
2026-05-05  5:04     ` Metzger, Markus T
2026-05-05 15:51       ` Simon Marchi
2026-05-06  5:43         ` Metzger, Markus T
2026-05-06 18:36           ` Simon Marchi
2026-05-07  7:36             ` Metzger, Markus T
2026-05-07 15:11               ` Simon Marchi
2026-05-11  7:25                 ` Metzger, Markus T
2026-05-11 10:05                   ` Metzger, Markus T
2026-05-12  6:36                     ` Metzger, Markus T
2026-05-13 14:33                     ` Tom Tromey
2026-05-13 17:05                       ` Tom Tromey
2026-05-14 22:07                   ` Thiago Jung Bauermann
2026-05-04  7:16 ` [PATCH] gdb, remote: fix notify debug nullptr dereference Markus Metzger
2026-05-04 15:40   ` Simon Marchi
2026-05-04  7:16 ` [PATCH] gdb, testsuite: increase timeout in gdb.threads/attach-non-stop.exp Markus Metzger
2026-05-04 15:49   ` Simon Marchi
2026-05-05  6:15     ` Metzger, Markus T
2026-05-05 15:54       ` Simon Marchi [this message]
2026-05-06  6:33         ` Metzger, Markus T
2026-05-04  7:16 ` [PATCH] gdb: update store_integer's comment Markus Metzger
2026-05-04 15:52   ` Simon Marchi
2026-05-04  7:16 ` [PATCH] gdb: use correct target in notify_thread_exited() Markus Metzger
2026-05-04 16:06   ` Simon Marchi
2026-05-05  7:56     ` Metzger, Markus T
2026-05-05 16:10       ` Simon Marchi
2026-05-06  6:56         ` Metzger, Markus T
2026-05-04  7:16 ` [PATCH v2] gdb, btrace: support libipt v2.2 events Markus Metzger
2026-05-04 12:08   ` Eli Zaretskii
2026-05-04 14:00     ` Metzger, Markus T
2026-05-04 15:04       ` Eli Zaretskii
2026-05-05  4:32         ` Metzger, Markus T
2026-05-05  5:12           ` Eli Zaretskii
2026-05-04 14:44 ` [PATCH] gdb, btrace: fix wrong #endif comments Simon Marchi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eb205100-f1ac-4f5f-8c5e-1b4c666735f5@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox