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/30289] [gdb/testsuite] Test run with editing off Date: Thu, 30 Mar 2023 11:06:11 +0000 [thread overview] Message-ID: <bug-30289-4717-ml7dct4yFz@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30289-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30289 --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- The tentative patch at PR30290 - "[gdb/tui] tui unusable with editing off" fixes a fair amount of the tui test-case fails. But it doesn't cover the ones that use readline bindings (arrow up etc), and also the output is not as expected for tui test-cases using python, haven't looked into that. Anyway, I think the fails fall into 3 categories: - sending more than one command to gdb at a time - tui - gdb prompt put into log file instead of stdout I was actually looking for instances of a 4th category: tab completion, but AFAICT those have all been fixed. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2023-03-30 11:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-30 2:52 [Bug testsuite/30289] New: " vries at gcc dot gnu.org 2023-03-30 11:06 ` vries at gcc dot gnu.org [this message]
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-30289-4717-ml7dct4yFz@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).