From: Peter Stephenson <p.stephenson@samsung.com>
To: Paul M <tallus@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: [BUG] Segfault when referencing $WIDGET in TRAPWINCH
Date: Tue, 07 Jun 2016 09:29:25 +0100 [thread overview]
Message-ID: <20160607092925.62d4ce36@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <1465281760.11740.13.camel@localhost>
On Mon, 06 Jun 2016 23:42:40 -0700
Paul M <tallus@gmail.com> wrote:
> Steps to reproduce:
>
> 1. add a TRAPWINCH something like this:
>
> TRAPWINCH(){echo $WIDGET}
>
> 2. Open a terminal
> 3. Resize
>
> zsh will segfault. GDB reports something like this
>
> Program received signal SIGSERV, Segmentation fault.
> 0xXXXXX.. in ?? () from /usr/lib/x86_64-linux-gnu/zsh/5.0.2/zsh/zle.so
I think that's been fixed --- I got it to happen easily with 5.0.2 but
it didn't with the latest version. 5.0.2 is a few years old.
pws
prev parent reply other threads:[~2016-06-07 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 6:42 Paul M
2016-06-07 8:29 ` Peter Stephenson [this message]
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=20160607092925.62d4ce36@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=tallus@gmail.com \
--cc=zsh-workers@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).