Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: More trap-handling crashes
- X-seq: zsh-workers 11856
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: More trap-handling crashes
- Date: Sat, 10 Jun 2000 19:28:38 +0000
- In-reply-to: <1000610185645.ZM29035@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <1000610182255.ZM28376@xxxxxxxxxxxxxxxxxxxxxxx> <1000610185645.ZM29035@xxxxxxxxxxxxxxxxxxxxxxx>
On Jun 10, 6:56pm, Bart Schaefer wrote:
}
} On Jun 10, 6:22pm, Bart Schaefer wrote:
} } I suspect this is related to the (root cause of the) TRAPEXIT crash
} } that Clint patched recently.
}
} I'm now completely convinced that the two are connected, and that testing
} for (st->list != NULL) is not a sufficient fix.
I've traced this to the point where parse.c:bld_eprog() does something
horribly wrong when handed a parse consisting of nothing but NULLTOK,
and now I'm beyond my understanding of what's supposed to be going on.
However, it sure looks like a bad interaction between the trap scoping
mechanism and eprogs for functions with empty bodies.
--
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author