public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jremus at linux dot ibm.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: Thu, 16 Jan 2025 12:33:13 +0000	[thread overview]
Message-ID: <bug-26116-4717-gfVVw2Xk33@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26116-4717@http.sourceware.org/bugzilla/>

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

Jens Remus <jremus at linux dot ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jremus at linux dot ibm.com

--- Comment #5 from Jens Remus <jremus at linux dot ibm.com> ---
Very annoying! Ran into this running the GDB testsuite on s390x. My shell is
zsh. Nearly all gdb.server tests hang and run into a timeout.

I could workaround by running the testsuite with SHELL=bash as follows:

$ SHELL=bash make check

Would it make sense to skip all gdb.server tests if the shell is one of the
known problematic ones or use --no-startup-with-shell in those tests?

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

  parent reply	other threads:[~2025-01-16 12:33 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
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 [this message]
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-gfVVw2Xk33@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).