Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [RFC][gdb/testsuite] Remove read1 timeout factor from gdb.base/info-macros.exp
Date: Fri, 25 Jun 2021 10:46:15 -0400	[thread overview]
Message-ID: <000fba5a-d926-27da-f313-94849cf7acea@polymtl.ca> (raw)
In-Reply-To: <20210624153449.GA30047@delia>

On 2021-06-24 11:34 a.m., Tom de Vries wrote:
> Hi,
> 
> At the moment some check-read1 timeouts are handled like this in
> gdb.base/info-macros.exp:
> ...
> gdb_test_multiple_with_read1_timeout_factor 10 "$test" $testname {
>   -re "$r1$r2$r3" {
>      pass $testname
>   }
>   -re ".*#define TWO.*\r\n$gdb_prompt" {
>      fail $testname
>   }
>   -re ".*#define THREE.*\r\n$gdb_prompt" {
>      fail $testname
>   }
>   -re ".*#define FOUR.*\r\n$gdb_prompt" {
>      fail $testname
>   }
> }
> ...
> which is not ideal.
> 
> We could use gdb_test_lines, but it currently doesn't support verifying
> the absence of regexps, which is currently implemented using the clauses above
> calling fail.
> 
> Fix this by using gdb_test_lines and adding a -re-not syntax to
> gdb_test_lines, such that we can do:
> ...
> gdb_test_lines $test $testname $r1.*$r2 \
>     -re-not "#define TWO" \
>     -re-not "#define THREE" \
>     -re-not "#define FOUR"
> ...
> 
> Only removing one use of gdb_test_multiple_with_read1_timeout_factor in the
> test-case for now.
> 
> Tested on x86_64-linux, which make targets check and check-read1.
> 
> Any comments?

I don't see anything wrong with the patch, seems useful.

Simon

  reply	other threads:[~2021-06-25 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 15:34 Tom de Vries
2021-06-25 14:46 ` Simon Marchi via Gdb-patches [this message]
2021-07-06 10:06   ` Tom de Vries

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=000fba5a-d926-27da-f313-94849cf7acea@polymtl.ca \
    --to=gdb-patches@sourceware.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