Re: TRAPINT doesn't work reliably

[Peter Stephenson <p.stephenson@xxxxxxxxxxx>]

On Wed, 2019-09-25 at 16:25 +0000, Dennis Schwartz wrote:
> ==1896==  Block was alloc'd at
> ==1896==    at 0x483877F: malloc (vg_replace_malloc.c:299)
> ==1896==    by 0x136A13: zcontext_save_partial (in /usr/bin/zsh)
> ==1896==    by 0x165622: parse_subscript (in /usr/bin/zsh)
> ==1896==    by 0x17A446: getindex (in /usr/bin/zsh)
> ==1896==    by 0x17ABCF: fetchvalue (in /usr/bin/zsh)
> ==1896==    by 0x19BDB0: ??? (in /usr/bin/zsh)
> ==1896==    by 0x1A0C87: prefork (in /usr/bin/zsh)
> ==1896==    by 0x13ABE6: execsubst (in /usr/bin/zsh)
> ==1896==    by 0x1674CB: execfor (in /usr/bin/zsh)
> ==1896==    by 0x13E44C: ??? (in /usr/bin/zsh)
> ==1896==    by 0x13FB6E: ??? (in /usr/bin/zsh)
> ==1896==    by 0x13FF11: ??? (in /usr/bin/zsh)
> ==1896==
> ==1896== Invalid read of size 1

One kind of interesting thing here is there's some suggestion that the
original allocation was not simply in top level code, but in some kind
of block (at least a for block) --- assuming, of course, this is
relevant.  Is there some structure about the point where you're setting
up the trap?  If so, does changing it (making it simpler) have any
effect on the problem?

Cheers
pws