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 gdb/29032] [gdb][test-case failure, taskset] FAIL: gdb.base/eof-exit.exp: with non-dump terminal: close GDB with eof (timeout) Date: Thu, 07 Apr 2022 10:00:13 +0000 [thread overview] Message-ID: <bug-29032-4717-cmcqo8mIpI@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29032-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29032 --- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> --- (In reply to Tom de Vries from comment #3) > This make the test-case pass reliably: But, runs into trouble in the test-suite: ... (gdb) ^M 100-gdb-set height 0^J100^done^M (gdb) ^M WARNING: Couldn't set the height to 0 101-gdb-set width 0^J101^done^M (gdb) ^M WARNING: Couldn't set the width to 0. ... The change doesn't sit well with terminals used for mi input. Now trying out moving the code to a place where it has less scope: ... diff --git a/gdb/event-top.c b/gdb/event-top.c index b628f0397cb..6fa0d492a2d 100644 --- a/gdb/event-top.c +++ b/gdb/event-top.c @@ -43,6 +43,7 @@ #include "async-event.h" #include "bt-utils.h" #include "pager.h" +#include "termios.h" /* readline include files. */ #include "readline/readline.h" @@ -1312,6 +1313,11 @@ gdb_setup_readline (int editing) one instance of readline. */ if (ISATTY (ui->instream) && editing && ui == main_ui) { + struct termios termios; + tcgetattr (0, &termios); + termios.c_lflag &= ~(ICANON); + tcsetattr (0, TCSANOW, &termios); + /* Tell gdb that we will be using the readline library. This could be overwritten by a command in .gdbinit like 'set editing on' or 'off'. */ ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-07 10:00 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-06 11:36 [Bug gdb/29032] New: " vries at gcc dot gnu.org 2022-04-06 11:36 ` [Bug gdb/29032] " vries at gcc dot gnu.org 2022-04-06 11:41 ` vries at gcc dot gnu.org 2022-04-07 8:02 ` vries at gcc dot gnu.org 2022-04-07 9:10 ` vries at gcc dot gnu.org 2022-04-07 10:00 ` vries at gcc dot gnu.org [this message] 2022-04-07 10:08 ` vries at gcc dot gnu.org 2022-04-07 10:32 ` vries at gcc dot gnu.org 2022-04-07 11:56 ` vries at gcc dot gnu.org 2022-04-07 12:44 ` aburgess at redhat dot com 2022-04-07 13:18 ` vries at gcc dot gnu.org 2022-04-07 14:44 ` vries at gcc dot gnu.org 2022-04-08 13:17 ` vries at gcc dot gnu.org 2022-04-08 15:37 ` vries at gcc dot gnu.org 2022-05-09 14:01 ` cvs-commit at gcc dot gnu.org 2022-05-25 8:20 ` [Bug gdb/29032] [gdb] ^D while not at prompt doesn't trigger quit 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-29032-4717-cmcqo8mIpI@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: linkBe 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).