Zsh Mailing List Archive
Messages sorted by:
Re: localtraps and signal handling on NetBSD
- X-seq: zsh-workers 21253
- From: Vincent Stemen <vince@xxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: localtraps and signal handling on NetBSD
- Date: Tue, 10 May 2005 13:46:01 -0500
- In-reply-to: <5415.1115631148@xxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20050425063521.GA17598@xxxxxxxxxxxxxxxxx> <1050425163202.ZM25027@xxxxxxxxxxxxxxxxxxxxxxx> <20050426030308.GA21501@xxxxxxxxxxxxxxxxx> <200504261834.j3QIYHSa018951@xxxxxxxxxxxxxx> <1050427053638.ZM28743@xxxxxxxxxxxxxxxxxxxxxxx> <200504270954.j3R9sujP029445@xxxxxxxxxxxxxx> <20050507171938.GA51740@xxxxxxxxxxxxxxxxx> <5415.1115631148@xxxxxxx>
On Mon, May 09, 2005 at 10:32:28AM +0100, Peter Stephenson wrote:
> Vincent Stemen wrote:
> > I was just wondering if you are planning to do any further work on the
> > signal/localtrap code.
> As far as I've followed the problems, they're mostly system specific.
> I'm sure there's more that can be done but I'm not really clear what.
> I'm not a great expert on signals anyway (traps are a little
Ok. For now, I found a not so clean work around for the code I am
working on, that would not necessarily work in other situations.
If you come up with any other ideas to try, I am willing to test for
you and assist in any way I can.
I did notice in the zsh source that it sets an intrap flag once a
signal has been received, which apparently causes it to treat the next
signal special by queuing it and waiting until it exits the signal
handler before processing it.
I have an idea, that might not be to difficult to implement, that I
think would solve the problem, unless you know of other problems it
If, inside the signal handler, I execute the trap statement on the
same signal, turn off the intrap status because the signal is now
I don't know the zsh source well enough to be sure where to make that
change, but from initial browsing, it looks like it might be easy to
Does that sound like something you would be willing to try, and send
me a patch to test on NetBSD?
Avoid the VeriSign/Network Solutions domain registration trap!
Read how Network Solutions (NSI) was involved in stealing our domain name.
Messages sorted by: