Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Luis Machado <luis.machado@linaro.org>,
	Tom de Vries <tdevries@suse.de>,
	gdb-patches@sourceware.org
Subject: Re: [committed][gdb/testsuite] Make gdb.mi/mi-sym-info.exp more robust against timeouts
Date: Fri, 30 Apr 2021 09:06:54 -0400	[thread overview]
Message-ID: <26770214-5135-391b-6bd0-4b5f39b97149@polymtl.ca> (raw)
In-Reply-To: <1c7ee1d2-9ff0-645c-3a0e-b6d1ed3f328f@linaro.org>

On 2021-04-30 8:55 a.m., Luis Machado via Gdb-patches wrote:
> Wouldn't it be more reliable to do line-by-line matching instead of sprinkling timeouts across the test? Or so I've been told.
> 
> This doesn't seem to be an instance where GDB is taking too long, but rather that the MI output is very verbose, right?

From what I can see, it's a case of GDB thinking for a long time
(gathering symbols) before outputting anything.  You can see it
by having a

  $ tail -F testsuite/gdb.log

on the side, while you run the test.

Another one that I found times out in a similar way on my machine is
gdb.base/info-os.exp.

Simon

  parent reply	other threads:[~2021-04-30 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30  9:27 Tom de Vries
2021-04-30 12:55 ` Luis Machado via Gdb-patches
2021-04-30 13:05   ` tdevries
2021-04-30 13:06   ` Simon Marchi via Gdb-patches [this message]
2021-04-30 13:20     ` Luis Machado via Gdb-patches
2021-04-30 13:28       ` Simon Marchi via Gdb-patches
2021-04-30 13:34         ` Luis Machado via Gdb-patches
2021-04-30 13:41           ` Simon Marchi via Gdb-patches

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=26770214-5135-391b-6bd0-4b5f39b97149@polymtl.ca \
    --to=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tdevries@suse.de \
    /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