From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: 3.0.6-pre-5 problem and loop killing
Date: Mon, 28 Jun 1999 10:04:48 +0400 [thread overview]
Message-ID: <000001bec12c$21186040$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <990625171454.ZM5335@candle.brasslantern.com>
>
> Which of course is the one thing Sven hasn't tried patching yet ... but I'm
> not sure WHY zsh is going through the third branch. All of Sven's patches
> have been to the second branch.
>
> What's odd is that over in the 6860 "Re: PATCH: loop killing" thread, zsh
> DOESN'T get the signal when it's supposed to. Maybe Sven's got the cases
> in which zsh takes the second and third branches, reversed?
>
Looking a bit more closely on truss of the two cases reveal, that they are quite
different:
this is from xterm -e zsh (the case, when ^Z does not work):
bor@itsrm2:~%> fgrep 'fork
execve
SIGCLD' /tmp/foo
8323: execve("/usr/bin/X11/xterm", 0x000000FFFFFEEC30, 0x000000FFFFFEEC40)
argc = 1
8323: fork() = 8324
8324: fork() (returning as child ...) = 8323
8324: sighold(SIGCLD) = SIG_DFL
8324: fork() = 8326
8323: signal(SIGCLD, 0x00000000004068E0) = SIG_DFL
8326: fork() (returning as child ...) = 8324
8326: execve("/usr/lib/pt_chmod", 0x000000007FFEE07C, 0x000000007FFEEDD4)
argc = 2
8324: sigrelse(SIGCLD) = SIG_DFL
8324: Received signal #18, SIGCLD [default]
8324: siginfo: SIGCLD CLD_EXITED pid=8326 uid=1 status=0x0000
8324: signal(SIGCLD, SIG_DFL) = SIG_DFL
8324: execve("/tools/bin/zsh", 0x000000007FFEE0CC, 0x000000000049CE90) argc =
1
8324: sigaction(SIGCLD, 0x000000007FFEEC60, 0x0000000000000000) = 0
8324: fork() = 8331
8331: fork() (returning as child ...) = 8324
8331: execve("/usr/bin/zcat", 0x0000000000502B28, 0x0000000000505780) argc =
1
8324: Received signal #18, SIGCLD, in sigsuspend() [caught]
8324: siginfo: SIGCLD CLD_KILLED pid=8331 uid=0 status=0x0002
8323: Received signal #18, SIGCLD, in poll() [caught]
8323: siginfo: SIGCLD CLD_EXITED pid=8324 uid=61 status=0x0082
bor@itsrm2:~%>
Note, that zsh doe exactly one fork/execve for zcat
And here is the same for the simple case zsh started from other zsh:
bor@itsrm2:/tools/src/zsh-3.1.5-pws-23%>
fgrep 'fork
execve
SIGCLD' /tmp/zsh.1}
12558: execve("/tools/bin/zsh", 0x000000FFFFFEECF0, 0x000000FFFFFEED00) argc =
1
12558: sigaction(SIGCLD, 0x000000007FFEED00, 0x0000000000000000) = 0
12558: fork() = 12559
12559: fork() (returning as child ...) = 12558
12559: execve("/usr/bin/zcat", 0x0000000000502D60, 0x00000000004FE5A0) argc =
1
12558: Received signal #18, SIGCLD, in sigsuspend() [caught]
12558: siginfo: SIGCLD CLD_STOPPED pid=12559 uid=0 status=0x0018
12558: fork() = 12561
12561: fork() (returning as child ...) = 12558
12558: Received signal #18, SIGCLD [caught]
12558: siginfo: SIGCLD CLD_STOPPED pid=12561 uid=0 status=0x0017
12558: Received signal #18, SIGCLD, in sigsuspend() [caught]
12558: siginfo: SIGCLD CLD_CONTINUED pid=12559 uid=0 status=0x0019
12558: Received signal #18, SIGCLD, in sigsuspend() [caught]
12558: siginfo: SIGCLD CLD_KILLED pid=12559 uid=0 status=0x0002
12558: Received signal #18, SIGCLD [caught]
12558: siginfo: SIGCLD CLD_CONTINUED pid=12561 uid=0 status=0x0019
12558: Received signal #18, SIGCLD [caught]
12558: siginfo: SIGCLD CLD_KILLED pid=12561 uid=0 status=0x0002
bor@itsrm2:/tools/src/zsh-3.1.5-pws-23%>
Here zsh forks once more. I have no idea, where lies the difference (apart from
these PGID/SID). Both are equally *not* login shells and source the same
scripts.
/andrej
prev parent reply other threads:[~1999-06-28 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-25 12:52 3.0.6-pre-5 problem Sven Wischnowsky
1999-06-25 15:56 ` Peter Stephenson
1999-06-25 16:17 ` Xterm terminal settings (Re: 3.0.6-pre-5 problem) Bart Schaefer
1999-06-25 16:29 ` 3.0.6-pre-5 problem Bart Schaefer
1999-06-25 17:14 ` Bart Schaefer
1999-06-28 6:04 ` Andrej Borsenkow [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='000001bec12c$21186040$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=schaefer@candle.brasslantern.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).