public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/26116] New: gdbserver with zsh as the shell hangs at startup when .zshenv forks
Date: Sun, 14 Jun 2020 02:49:04 +0000	[thread overview]
Message-ID: <bug-26116-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26116
           Summary: gdbserver with zsh as the shell hangs at startup when
                    .zshenv forks
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: simark at simark dot ca
  Target Milestone: ---

When using zsh as the shell and a command that forks in ~/.zshenv, like
`/bin/echo` here (plain `echo` is the shell builtin, which doesn't fork):

$ cat ~/.zshenv 
echo Before
/bin/echo Hello
echo After

... gdbserver hangs at startup

$ SHELL=zsh ./gdbserver localhost:9000 /bin/ls 
Before
Hello
<hangs here>

Note that when using a similar bash feature, the BASH_ENV environment variable,
it doesn't hang:

$ SHELL=bash BASH_ENV=~/.zshenv ./gdbserver localhost:9000 /bin/ls 
Before
Hello
After
Process /bin/ls created; pid = 745096
Listening on port 9000

It's also possible that the issue is in zsh, but I haven't dug enough to
understand what's happening exactly.

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

             reply	other threads:[~2020-06-14  2:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14  2:49 simark at simark dot ca [this message]
2020-12-04  6:23 ` [Bug server/26116] " dajiang0055 at gmail dot com
2021-05-05  2:14 ` corydoras at ridiculousfish dot com
2024-04-22 12:44 ` k4lizen at proton dot me

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-26116-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).