public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "corydoras at ridiculousfish dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/26116] gdbserver with zsh as the shell hangs at startup when .zshenv forks
Date: Wed, 05 May 2021 02:14:01 +0000	[thread overview]
Message-ID: <bug-26116-4717-DunEpbu1wd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26116-4717@http.sourceware.org/bugzilla/>

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

ridiculous_fish <corydoras at ridiculousfish dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |corydoras at ridiculousfish dot co
                   |                            |m

--- Comment #2 from ridiculous_fish <corydoras at ridiculousfish dot com> ---
fish shell is also seeing this - see
https://github.com/fish-shell/fish-shell/issues/7957

My investigation got as far as follows: gdbserver forks in preparation for
exec'ing the shell. Before exec, it requests ptrace on itself (in
`linux_ptrace_fun`). This causes signals to be delivered to gdbserver before
the inferior shell; however gdbserver does not then arrange for the signal to
be delivered to the shell so it is dropped. fish (and presumably zsh) relies on
SIGCHLD to reap processes, so fish ends up hanging.

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

  parent reply	other threads:[~2021-05-05  2:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14  2:49 [Bug server/26116] New: " simark at simark dot ca
2020-12-04  6:23 ` [Bug server/26116] " dajiang0055 at gmail dot com
2021-05-05  2:14 ` corydoras at ridiculousfish dot com [this message]
2024-04-22 12:44 ` k4lizen at proton dot me
2024-09-25 19:57 ` tromey at sourceware dot org
2025-01-16 12:33 ` jremus at linux dot ibm.com
2025-01-24 15:39 ` sam at gentoo dot 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-26116-4717-DunEpbu1wd@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).