Re: TRAPINT doesn't work reliably

[Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>]

Dennis Schwartz wrote on Sat, Sep 28, 2019 at 11:16:08 +0000:
> I have run
> 
> $ ./configure --enable-zsh-debug --enable-zsh-mem && make && sudo make install

Please run «make check» in there as well, on general principles.

> On Friday, September 27, 2019 1:46 PM, Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> wrote:
> 
> > Dennis Schwartz wrote on Thu, 26 Sep 2019 17:10 +00:00:
> >
> > > $ valgrind --leak-check=full --log-file=zsh-valgrind.log /usr/local/bin/zsh
> > > /usr/share/zsh-antigen/antigen.zsh:2134: parse error near `\n'
> > > $ ll
> >
> > What's the output of `dpkg -l zsh-antigen`? (I'm looking for the version number.)
> 
> Good point. Debian 10 (buster) ships 2.2.3-2, which I'm running.
> I believe the bug is triggered in zsh by using this newer version
> (Debian 9 ships 1.3.4-1). If I compile and run zsh 5.3.1 (shipped with
> Debian 9, where I did not encountered this issue) on with `zsh-antigen`
> from Debian 10, I can also trigger the bug.

Okay, so we have another angle on this: we could try to bisect antigen,
either temporally (between 1.3.4-1 in Debian stretch and 2.2.3-2 in
Debian buster) or spatially (taking the 2.2.3-2 version and deleting
half of its antigen.zsh file at a time, lather, rinse, repeat).

Would it be worthwhile to try and find a minimal example for the parse
error?  I don't know whether it's likely to be related to the memory
bug.

> > Does removing that assignment make a difference?
> 
> No, the bug triggers for any TRAPINT function I've tried so far.

Have you tried an empty function, «TRAPINT () {}»?

Is there any reason to also try a «trap ':' INT»?

Cheers,

Daniel