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/26952] New: FAIL: gdb.base/multi-line-starts-subshell.exp: spawn subshell from multi-line (timeout)
Date: Thu, 26 Nov 2020 14:47:00 +0000	[thread overview]
Message-ID: <bug-26952-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26952
           Summary: FAIL: gdb.base/multi-line-starts-subshell.exp: spawn
                    subshell from multi-line (timeout)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

...
(gdb) if 1^M
 >shell HOME=/dev/null PS1="gdb-subshell$ " /bin/sh^M
 >end^M
hostname:/dir> FAIL: gdb.base/multi-line-starts-subshell.exp: spawn subshell
from multi-line (timeout)
...

The PS1 setting doesn't seem to have an effect:
...
$ HOME=/dev/null PS1="gdb-subshell$ " /bin/sh 
hostname:/dir> 
hostname:/dir> echo $PS1
\h:\w>
hostname:/dir> echo $HOME
/dev/null
...
while the HOME setting does.

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

             reply	other threads:[~2020-11-26 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 14:47 vries at gcc dot gnu.org [this message]
2020-11-26 16:34 ` [Bug testsuite/26952] " vries at gcc dot gnu.org
2020-12-14  6:56 ` vries at gcc dot gnu.org
2020-12-15  9:18 ` cvs-commit at gcc dot gnu.org
2020-12-15  9: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-26952-4717@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).