From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id mAO8Ob+8dWRSmBgAWB0awg (envelope-from ) for ; Tue, 30 May 2023 05:07:11 -0400 Received: by simark.ca (Postfix, from userid 112) id E90471E11E; Tue, 30 May 2023 05:07:11 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=Xob/KGK4; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_MED,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 6592C1E0D4 for ; Tue, 30 May 2023 05:07:11 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id CAC54385702F for ; Tue, 30 May 2023 09:07:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CAC54385702F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1685437630; bh=IDukCxxCKWlxhOHxwD3Z1S5rBdvrq97XOv6DcyyAV48=; h=Date:Subject:To:Cc:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=Xob/KGK4t3acBxIPIWLZxQlYXEITCtOl2tAQ11mBI32d+FQ5QC6hpxFX1x4SGcd50 QUUDtDDH92CJJHiUSkzv5VuWCqiKlTRyQOydKT0jM8K52qSiItMJX0byYaA5FYB6TR lOIu7tqg9sBAd2nnl1RMUsSxnLoL29N6bhiCBNrc= Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by sourceware.org (Postfix) with ESMTPS id C5FAC3856DE6 for ; Tue, 30 May 2023 09:06:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C5FAC3856DE6 Received: from imap1.suse-dmz.suse.de (imap1.suse-dmz.suse.de [192.168.254.73]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id E278321A0D; Tue, 30 May 2023 09:06:40 +0000 (UTC) Received: from imap1.suse-dmz.suse.de (imap1.suse-dmz.suse.de [192.168.254.73]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap1.suse-dmz.suse.de (Postfix) with ESMTPS id C20D71341B; Tue, 30 May 2023 09:06:40 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap1.suse-dmz.suse.de with ESMTPSA id oazMLaC8dWQ4IAAAGKfGzw (envelope-from ); Tue, 30 May 2023 09:06:40 +0000 Message-ID: Date: Tue, 30 May 2023 11:06:39 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.tui/wrap-line.exp To: Andrew Burgess , gdb-patches@sourceware.org Cc: Simon Marchi References: <20230518061046.17837-1-tdevries@suse.de> <87ilcm83tt.fsf@redhat.com> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Tom de Vries via Gdb-patches Reply-To: Tom de Vries Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 5/21/23 18:48, Tom de Vries wrote: > On 5/21/23 10:51, Andrew Burgess wrote: >> Tom de Vries via Gdb-patches writes: >> >>> 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. >> >> Do we know why we sometimes manage to see '^C'?  I guess it's a timing >> thing, but right now I'm at a loss for how we manage to see it.  It >> appears that we print the wrapping line, that ends with 'W', and then >> wait for this to be displayed. >> >> At this point GDB should be in a stable state waiting in the >> event-loop. >> >> When we send \003 this should trigger an event, which should trigger >> async_request_quit, which should result in the 'Quit' exception being >> thrown, caught, and printed. >> >> I think the '^C' must be getting printed from tui_redisplay_readline >> maybe, but I can't see how that gets triggered with \003 in the input >> buffer. >> >> I only ask because if we understand why '^C' is sometimes printed then >> we might be able to decide if this should always be printed, or never be >> printed, and change GDB accordingly... >> > > Hi Andrew, > > yes, that's a good question. > > [ Note that it's a TUI test-case, but the FAIL we're observing is in the > cli part, before activating TUI, so tui_redisplay_readline has nothing > to do with the FAIL. ] > > I've added an assert in rl_echo_signal_char and managed to trigger it to > generate a core file corresponding to the FAIL condition (more details > in the PR). > > My guess at what happens is the following: > - we send a W to gdb > - readline handles this, and echoes it > - after readline echoing it, expect notices this and we send a ^C to gdb > - at this point readline is still in the code handling the W, and >   handles the ^C by echoing it. > > Usually, at this point we're already back in gdb and handle the ^C > without echoing it. > Andrew, any comment? Thanks, - Tom > Thanks, > - Tom > >> Thanks, >> Andrew >> >>> >>> Tested on x86_64-linux. >>> >>> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30458 >>> --- >>>   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 >>> -- >>> 2.35.3 >> >