Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Z shell signal handling
- X-seq: zsh-workers 21265
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Z shell signal handling
- Date: Tue, 17 May 2005 15:42:09 +0000
- In-reply-to: <20050517081513.GA93407@xxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20050426030308.GA21501@xxxxxxxxxxxxxxxxx> <200504261834.j3QIYHSa018951@xxxxxxxxxxxxxx> <1050427053638.ZM28743@xxxxxxxxxxxxxxxxxxxxxxx> <200504270954.j3R9sujP029445@xxxxxxxxxxxxxx> <20050507171938.GA51740@xxxxxxxxxxxxxxxxx> <5415.1115631148@xxxxxxx> <20050510184600.GA67763@xxxxxxxxxxxxxxxxx> <200505131127.j4DBR0Yt014380@xxxxxxxxxxxxxx> <20050514043338.GA82132@xxxxxxxxxxxxxxxxx> <200505161046.j4GAknfO018203@xxxxxxxxxxxxxx> <20050517081513.GA93407@xxxxxxxxxxxxxxxxx>
On May 17, 3:15am, Vincent Stemen wrote:
} Subject: Re: Z shell signal handling
}
} There are a couple potential problems I can see with the sh approach,
} that I am guessing zsh and bash were trying to fix.
The biggest problem is that C library routines like malloc() are not
re-entrant, and are heavily used by the shell. The issue is not with
race conditions, etc., at the level of shell function execution, but
deep within the shell implementation, possibly in places that are not
within the shell implementer's control.
When PWS speaks about whether it's "safe" to enable signals, he means
that if it's NOT safe, the shell is going to corrupt memory, possibly
crash, or even open holes in system security. Behaving the way that
the script programmer expects is secondary to these considerations.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author