public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/30458] FAIL: gdb.tui/wrap-line.exp: width-auto-detected: cli: prompt after wrap
Date: Sun, 21 May 2023 16:18:57 +0000	[thread overview]
Message-ID: <bug-30458-4717-7gps7GA0de@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30458-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30458

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #3)
> Passes reliably with:

Alternatively:
...
diff --git a/gdb/testsuite/lib/tuiterm.exp b/gdb/testsuite/lib/tuiterm.exp
index 64a883e89a3..a4c9e598a65 100644
--- a/gdb/testsuite/lib/tuiterm.exp
+++ b/gdb/testsuite/lib/tuiterm.exp
@@ -652,7 +652,7 @@ namespace eval Term {
     # Initialize.
     proc _setup {rows cols} {
        global stty_init
-       set stty_init "rows $rows columns $cols"
+       set stty_init "rows $rows columns $cols -ctlecho"

        variable _rows
        variable _cols
...

Both these are related to this condition:
...
rl_echo_signal_char (int sig)
{
  ...

  if (_rl_echoctl == 0 || _rl_echo_control_chars == 0)
    return;
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-05-21 16:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 15:07 [Bug gdb/30458] New: " simon.marchi at polymtl dot ca
2023-05-18  6:08 ` [Bug testsuite/30458] " vries at gcc dot gnu.org
2023-05-18  6:11 ` vries at gcc dot gnu.org
2023-05-21 16:02 ` vries at gcc dot gnu.org
2023-05-21 16:03 ` vries at gcc dot gnu.org
2023-05-21 16:09 ` vries at gcc dot gnu.org
2023-05-21 16:18 ` vries at gcc dot gnu.org [this message]
2023-05-21 16:21 ` vries at gcc dot gnu.org
2023-06-21 14:16 ` cvs-commit at gcc dot gnu.org
2023-06-21 14:19 ` vries at gcc dot gnu.org

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=bug-30458-4717-7gps7GA0de@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).