public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@redhat.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.tui/wrap-line.exp
Date: Fri, 19 May 2023 12:12:54 +0200	[thread overview]
Message-ID: <5691174a-f5df-629d-ae46-4012c7814bff@redhat.com> (raw)
In-Reply-To: <20230518061046.17837-1-tdevries@suse.de>

On 18/05/2023 08:10, Tom de Vries via Gdb-patches wrote:
> PR testsuite/30458 reports the following FAIL:
> ...
> PASS: gdb.tui/wrap-line.exp: width-auto-detected: cli: wrap
> ^CQuit
> (gdb) WARNING: timeout in accept_gdb_output
> Screen Dump (size 50 columns x 24 rows, cursor at column 6, row 3):
>      0 Quit
>      1 (gdb) 7890123456789012345678901234567890123456789
>      2 W^CQuit
>      3 (gdb)
>    ...
> FAIL: gdb.tui/wrap-line.exp: width-auto-detected: cli: prompt after wrap
> ...
>
> The problem is that the regexp doesn't account for the ^C:
> ...
>      gdb_assert { [Term::wait_for "^WQuit"] } "prompt after wrap"
> ...
>
> Fix this by updating the regexp, and likewise in another place in the
> test-case where we use ^C.
>
> Tested on x86_64-linux.
>
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30458
> ---

Hi Tom,

I can't seem to reproduce that bug, but this change also doesn't add any 
failures so it seems fine to me.

Tested-By: Bruno Larsen <blarsen@redhat.com>

-- 
Cheers,
Bruno

>   gdb/testsuite/gdb.tui/wrap-line.exp | 6 ++++--
>   1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.tui/wrap-line.exp b/gdb/testsuite/gdb.tui/wrap-line.exp
> index 4587517504c..2bfe342e04d 100644
> --- a/gdb/testsuite/gdb.tui/wrap-line.exp
> +++ b/gdb/testsuite/gdb.tui/wrap-line.exp
> @@ -25,6 +25,8 @@ set cols 50
>   set lines 24
>   set dims [list $lines $cols]
>   
> +set re_control_c "(\\^C)?Quit"
> +
>   # Fill line, assuming we start after the gdb prompt.
>   proc fill_line { width } {
>       set res ""
> @@ -47,7 +49,7 @@ proc fill_line { width } {
>   proc test_wrap { wrap_width } {
>       # Generate a prompt and parse it.
>       send_gdb "\003"
> -    gdb_assert { [Term::wait_for "(^|$::gdb_prompt )Quit"] } "start line"
> +    gdb_assert { [Term::wait_for "(^|$::gdb_prompt )$::re_control_c"] } "start line"
>   
>       # Fill the line to just before wrapping.
>       set str [fill_line $wrap_width]
> @@ -64,7 +66,7 @@ proc test_wrap { wrap_width } {
>   
>       # Generate a prompt and parse it.
>       send_gdb "\003"
> -    gdb_assert { [Term::wait_for "^WQuit"] } "prompt after wrap"
> +    gdb_assert { [Term::wait_for "^W$::re_control_c"] } "prompt after wrap"
>   }
>   
>   # Test wrapping in both CLI and TUI.
>
> base-commit: 0cc8cc5e6f82b8d3d8e3803c6f7f5e63f0c866ad


  reply	other threads:[~2023-05-19 10:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  6:10 Tom de Vries
2023-05-19 10:12 ` Bruno Larsen [this message]
2023-05-21  8:51 ` Andrew Burgess
2023-05-21  9:00   ` Andreas Schwab
2023-05-23  9:34     ` Andrew Burgess
2023-05-21 16:48   ` Tom de Vries
2023-05-30  9:06     ` Tom de Vries
2023-05-30 10:12       ` Andrew Burgess
2023-05-30 13:45     ` Andrew Burgess
2023-05-31 15:49       ` Tom de Vries
2023-06-01 11:12         ` Andrew Burgess
2023-06-21 14:19           ` Tom de Vries
2023-06-21 14:24             ` 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=5691174a-f5df-629d-ae46-4012c7814bff@redhat.com \
    --to=blarsen@redhat.com \
    --cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).