From: Alexey Tourbin <at@altlinux.ru>
To: zsh-workers@sunsite.dk
Subject: Re: recent zsh-4.3.0 snapshot hangs
Date: Tue, 19 Jul 2005 12:54:29 +0400 [thread overview]
Message-ID: <20050719085429.GA24898@solemn.turbinal.org> (raw)
In-Reply-To: <1050718152936.ZM5991@candle.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On Mon, Jul 18, 2005 at 03:29:36PM +0000, Bart Schaefer wrote:
> On Jul 18, 2:17pm, Alexey Tourbin wrote:
> }
> } Here is strace log for HOSTNAME=`/bin/hostname`:
> }
> } pause(
>
> What platform is this? (Linux, but can you be more specific? Is it
> multiprocessor or otherwise using an SMP kernel?)
$ uname -rms
Linux 2.4.20-alt7-up i686
$ rpm -q glibc
glibc-2.3.3.200406160000-alt1
$
> Unless your config.h defines BROKEN_POSIX_SIGSUSPEND, there's only
> one call to pause() in the sources, in signal_suspend().
One important thing I didn't realize until now: the whole build process
was run under strace(1). (Don't ask me why. (In short, this was
build-time dependency analysis.))
So I tend to blame strace now, since it does some clever mangling
which affects process control behaviour, which in turn could affect
configure tests:
If the parent process decides to wait(2) for a child
that is currently being traced, it is suspended
until an appropriate child process either terminates
or incurs a signal that would cause it to terminate
(as determined from the child's current signal dis-
position).
Now I'm trying to find out the exact reason.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-07-19 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 8:49 Alexey Tourbin
2005-07-18 9:21 ` Alexey Tourbin
2005-07-18 9:47 ` Peter Stephenson
2005-07-18 10:17 ` Alexey Tourbin
2005-07-18 15:29 ` Bart Schaefer
2005-07-19 8:54 ` Alexey Tourbin [this message]
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=20050719085429.GA24898@solemn.turbinal.org \
--to=at@altlinux.ru \
--cc=zsh-workers@sunsite.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).