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/26951] FAIL: gdb.base/batch-preserve-term-settings.exp: batch run: spawn shell (timeout) Date: Thu, 26 Nov 2020 16:41:09 +0000 [thread overview] Message-ID: <bug-26951-4717-rUuxyWNRWj@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26951-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26951 --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- Tentative patch: ... diff --git a/gdb/testsuite/gdb.base/batch-preserve-term-settings.exp b/gdb/testsuite/gdb.base/batch-preserve-term-settings.exp index 7ae3518..b0abe3f 100644 --- a/gdb/testsuite/gdb.base/batch-preserve-term-settings.exp +++ b/gdb/testsuite/gdb.base/batch-preserve-term-settings.exp @@ -28,12 +28,13 @@ if [is_remote host] { } # The shell's prompt. -set shell_prompt_re "\[$#\] " +set shell_prompt "gdb-subshell$ " +set shell_prompt_re [string_to_regexp $shell_prompt] # Spawn shell. Returns true on success, false otherwise. proc spawn_shell {} { - global shell_prompt_re + global shell_prompt shell_prompt_re set res [remote_spawn host "/bin/sh"] if { $res < 0 || $res == "" } { @@ -41,6 +42,8 @@ proc spawn_shell {} { return 0 } + send_gdb "PS1=\"$shell_prompt\"\n" + set gotit 0 set test "spawn shell" gdb_expect { ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-26 16:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-26 14:02 [Bug testsuite/26951] New: " vries at gcc dot gnu.org 2020-11-26 16:41 ` vries at gcc dot gnu.org [this message] 2020-12-14 6:55 ` [Bug testsuite/26951] " vries at gcc dot gnu.org 2020-12-14 16:05 ` cvs-commit at gcc dot gnu.org 2020-12-14 16:06 ` 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-26951-4717-rUuxyWNRWj@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).