zsh-users
 help / color / mirror / code / Atom feed
From: Dennis Schwartz <dennis.schwartz@protonmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: "zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: TRAPINT doesn't work reliably
Date: Wed, 25 Sep 2019 13:02:48 +0000	[thread overview]
Message-ID: <Bczpjmkq93UC9ogVXedAec4MSWn1xm79AtK56m7J7_XKU3g1oWkhoUeoj9_CjqM_bdhDM3WFcb0IWT04yMJctdhKDGj_fiAyOLAfaMatz5k=@protonmail.com> (raw)
In-Reply-To: <1569314663.5531.4.camel@samsung.com>

On Tuesday, September 24, 2019 10:44 AM, Peter Stephenson <p.stephenson@samsung.com> wrote:

> On Tue, 2019-09-17 at 16:47 +0000, Dennis Schwartz wrote:
>
> > I have a function on TRAPINT in my .zshrc like described as in the Zsh manual [1].
> >  
> >      TRAPINT() {
> >          echo "trap: $1"
> >          return $(( 128 + $1 ))
> >      }
> >  
> >  
> > This works unreliably. Usually this works a first few times, but after a while this doesn’t work anymore and throws the following error.
> >  
> > TRAPINT:1: command not found: \M-^A^A
> > TRAPINT:2: command not found: F^\V
>
> This certainly isn't likely to be anything you've done wrong, at least based on
> what you've told us.
>
> It smells of memory management problems, but it's hard to see where the corruption
> would be.
>
> What do you see if you run
>
> functions TRAPINT
>
> after the problem has turned up?

It almost looks like the function gets replaced with random memory.
`functions TRAPINT` just shows random bytes, for example:

$ xxd <(functions TRAPINT)
00000000: 5452 4150 494e 5420 2829 207b 0a09 0701  TRAPINT () {....
00000010: 200a 0950 200a 7d0a                       ..P .}.


I am now more convinced it's a bug in Zsh. Any advice on how to debug this?
And where can I best submit a bug report to?


Dennis

  reply	other threads:[~2019-09-25 13:03 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 [this message]
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
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='Bczpjmkq93UC9ogVXedAec4MSWn1xm79AtK56m7J7_XKU3g1oWkhoUeoj9_CjqM_bdhDM3WFcb0IWT04yMJctdhKDGj_fiAyOLAfaMatz5k=@protonmail.com' \
    --to=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).