zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: bobort@bigfoot.com, zsh-workers@sunsite.auc.dk
Subject: Re: zsh bug-hang on startup after exec
Date: Thu, 22 Mar 2001 01:01:38 +0000	[thread overview]
Message-ID: <1010322010138.ZM19106@candle.brasslantern.com> (raw)
In-Reply-To: <XFMail.20010321132500.bobort@abacus.dorm.reed.edu>

On Mar 21,  1:25pm, Ryan Richter wrote:
} Subject: zsh bug-hang on startup after exec
}
} I had been using bash as my login shell, and had it set up to exec
} zsh. I just upgraded zsh from 3.1.6 to 3.1.9, and when I log in, zsh
} hangs immediately after being execed, before it even processes the
} startup scripts.

The strace output shows that it's getting stuck in this loop in init.c:

            while ((ttpgrp = gettygrp()) != -1 && ttpgrp != mypgrp) {
                sleep(1);       /* give parent time to change pgrp */
                mypgrp = GETPGRP();
                if (mypgrp == mypid)
                    attachtty(mypgrp);
                if (mypgrp == gettygrp())
                    break;
                killpg(mypgrp, SIGTTIN);
                mypgrp = GETPGRP();
            }

Why zsh is not becoming the process group leader, I don't know.  Obviously
bash must be exec'ing it before making *itself* the process group leader,
but then who *is* the group leader, a?

Note that

getpid()                                = 20122
getpgrp()                               = 20120
ioctl(10, TIOCGPGRP, [20121])           = 0

So there are at least three processes involved here ... the process group
leader is 20120 (whatever that was), but the tty group leader is 20121,
and neither of those is zsh (20122), so (mypgrp == mypid) is never going
to be true.

} Anyway, this is a linux 2.2.19 i686 system with glibc 2.1.3, and zsh was
} compiled with egcs 1.1.2.

Why does everyone always identify their Linux system by kernel version and
glibc version?  That's almost never enough information.  The vendor (e.g.
redhat) and vendor's version number (e.g. 7.1) are almost always much more
useful.  In this case it'd also be nice to know how you're logging in; is
it on the text console?  Remote shell?  XDM console?  If the latter, are
you using vanilla XDM, KDE, Gnome, or something else?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2001-03-22  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 21:25 Ryan Richter
2001-03-22  1:01 ` Bart Schaefer [this message]
2001-03-22  1:56   ` Ryan Richter
2001-03-22 16:56     ` Bart Schaefer
2001-03-22 17:02       ` Ryan Richter
2001-03-25 21:07         ` Bart Schaefer
2001-03-25 22:34           ` Ryan Richter
2001-03-28  5:48             ` Bart Schaefer

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=1010322010138.ZM19106@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=bobort@bigfoot.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).