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

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


  parent reply	other threads:[~2019-09-25 17:56 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 [this message]
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=1569434163.10786.26.camel@samsung.com \
    --to=p.stephenson@samsung.com \
    --cc=dennis.schwartz@protonmail.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).