From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Dennis Schwartz <dennis.schwartz@protonmail.com>
Cc: Peter Stephenson <p.stephenson@samsung.com>, zsh-users@zsh.org
Subject: Re: TRAPINT doesn't work reliably
Date: Sat, 28 Sep 2019 14:29:57 +0000 [thread overview]
Message-ID: <20190928142957.ertue2us5ytn6ooo@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <ODmJIQmuJJcZdaTGdd_T4zXxU0G7RHNJl3pSGxRC3qTePtsFsXSosieytwRTp2x2GTxggH_l9ZGZQb19rELfq70ZCOU9Xtr0Ik4ks9SpbOQ=@protonmail.com>
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@daniel.shahaf.name> 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
next prev parent reply other threads:[~2019-09-28 14:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190917164905epcas1p4ad458ffcd504501780d522880c81de3e@epcas1p4.samsung.com>
2019-09-17 16:47 ` Dennis Schwartz
2019-09-24 8:44 ` Peter Stephenson
2019-09-25 13:02 ` Dennis Schwartz
2019-09-25 14:01 ` Peter Stephenson
2019-09-25 16:25 ` Dennis Schwartz
2019-09-25 17:04 ` Peter Stephenson
2019-09-25 18:46 ` Daniel Shahaf
2019-09-26 15:27 ` Peter Stephenson
2019-09-27 13:43 ` Daniel Shahaf
2019-09-25 17:56 ` Peter Stephenson
2019-09-26 14:48 ` Dennis Schwartz
2019-09-26 15:25 ` Peter Stephenson
2019-09-26 17:10 ` Dennis Schwartz
2019-09-27 13:46 ` Daniel Shahaf
2019-09-28 11:16 ` Dennis Schwartz
2019-09-28 14:29 ` Daniel Shahaf [this message]
2019-09-28 18:21 ` Dennis Schwartz
2019-09-28 18:58 ` Dennis Schwartz
2019-09-28 16:00 ` Bart Schaefer
2019-09-29 16:54 ` Peter Stephenson
2019-09-27 19:05 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190928142957.ertue2us5ytn6ooo@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=dennis.schwartz@protonmail.com \
--cc=p.stephenson@samsung.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).