Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simon.marchi@efficios.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: fix gdb.base/ui-redirect.exp pattern (gdb/26532)
Date: Tue, 25 Aug 2020 16:55:35 +0200	[thread overview]
Message-ID: <6f8a87d1-489b-fb00-9f86-4584e0510557@suse.de> (raw)
In-Reply-To: <2ee8506c-2464-01a3-efa4-c5ec12786b2e@efficios.com>

On 8/25/20 4:49 PM, Simon Marchi wrote:
> On 2020-08-25 10:35 a.m., Tom de Vries wrote:
>> On 8/25/20 3:27 PM, Simon Marchi wrote:
>>> Commit 1eb8556f5a8b ("gdb: add infrun_debug_printf macro") changed the
>>> debug output format for `set debug infrun 1`.  It broke test
>>> gdb.base/ui-redirect.exp, which I missed:
>>>
>>>     FAIL: gdb.base/ui-redirect.exp: debugging: continue
>>>
>>
>> How about the other fail:
>> ...
>> FAIL: gdb.threads/stepi-random-signal.exp: stepi (no random signal)
>> ...
>>
>> ?
> 
> Oh, I missed your second message.  Damn, I updated this test, changed the output format
> later and forgot to update the test again.>  See patch below.
> 
> 
> From fc6c77211da34d18c2285347b6e400a3cd055b9f Mon Sep 17 00:00:00 2001
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Date: Tue, 25 Aug 2020 10:41:56 -0400
> Subject: [PATCH] gdb/testsuite: fix gdb.threads/stepi-random-signal.exp
>  pattern
> 
> Commit 1eb8556f5a8b ("gdb: add infrun_debug_printf macro") changed the
> debug output format for `set debug infrun 1`.  The test
> gdb.threads/stepi-random-signal.exp uses that debug output, and was
> updated, but not correctly.  It results in this failure:
> 
>     FAIL: gdb.threads/stepi-random-signal.exp: stepi (no random signal)
> 
> Fix it by adjusting the pattern in the test.
> 

Ack, I've tested both patches, and the FAILs are gone.

This patch could also use the PR line, not sure if you want to commit it
separately.

Anyway, LGTM.

Thanks,
- Tom

> gdb/testsuite/ChangeLog:
> 
> 	* gdb.threads/stepi-random-signal.exp: Update pattern.
> 
> Change-Id: If5fa525e9545e32a286effe6a6184358374bd37c
> ---
>  gdb/testsuite/gdb.threads/stepi-random-signal.exp | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gdb/testsuite/gdb.threads/stepi-random-signal.exp b/gdb/testsuite/gdb.threads/stepi-random-signal.exp
> index fa20f38ba61e..9a8b38c2acf5 100644
> --- a/gdb/testsuite/gdb.threads/stepi-random-signal.exp
> +++ b/gdb/testsuite/gdb.threads/stepi-random-signal.exp
> @@ -87,7 +87,7 @@ set seen 0
> 
>  set test "stepi"
>  if {[gdb_test_multiple "stepi" "$test" {
> -    -re "infrun: handle_signal_stop: random signal" {
> +    -re {\[infrun\] handle_signal_stop: random signal} {
>  	set seen 1
>  	exp_continue
>      }
> 


  reply	other threads:[~2020-08-25 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 13:27 Simon Marchi
2020-08-25 14:35 ` Tom de Vries
2020-08-25 14:49   ` Simon Marchi
2020-08-25 14:55     ` Tom de Vries [this message]
2020-08-25 15:01       ` 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=6f8a87d1-489b-fb00-9f86-4584e0510557@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.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