From: Eduardo Bustamante <dualbus@gmail.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@zsh.org
Subject: Re: Zsh parser segmentation fault on taddstr
Date: Sun, 7 May 2017 20:59:50 -0500 [thread overview]
Message-ID: <CAOSMAuvXZDpGOgr7W7Vx0ADWBHHYGoXSWRLaUPXUSG9pmO_7XQ@mail.gmail.com> (raw)
In-Reply-To: <20170507213631.2a15e7ad@ntlworld.com>
On Sun, May 7, 2017 at 3:36 PM, Peter Stephenson
<p.w.stephenson@ntlworld.com> wrote:
[...]
> I haven't got an actual crash, but I am getting some undefined behaviour
> which could do anything so is probably down to the same cause. I can
> get the same behaviour here:
FWIW, I built Zsh this way:
CC=clang CFLAGS='-O0 -ggdb' LDFLAGS='' ./configure
zsh configuration
-----------------
zsh version : 5.3.1-dev-0
host operating system : x86_64-unknown-linux-gnu
source code location : .
compiler : clang
preprocessor flags :
executable compiler flags : -O0 -ggdb
module compiler flags : -O0 -ggdb -fPIC
executable linker flags : -rdynamic
module linker flags : -shared
library flags : -ldl -ltinfo -lrt -lm -lc
installation basename : zsh
binary install path : /usr/local/bin
man page install path : /usr/local/share/man
info install path : /usr/local/share/info
functions install path : /usr/local/share/zsh/5.3.1-dev-0/functions
See config.modules for installed modules and functions.
dualbus@debian:~/src/zsh/zsh$ md5sum crash
c6abfc1333f1b544789e8578d54e1b60 crash
dualbus@debian:~/src/zsh/zsh$ base64 crash
aWYgKGEp/wAAPDwF/wkGfCYEXA==
dualbus@debian:~/src/zsh/zsh$ ./Src/zsh -nv crash
if (a)�<<� |&\Segmentation fault
next prev parent reply other threads:[~2017-05-08 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 16:45 Eduardo Bustamante
2017-05-07 20:36 ` Peter Stephenson
2017-05-08 1:59 ` Eduardo Bustamante [this message]
2017-05-08 9:37 ` Peter Stephenson
2017-05-08 13:51 ` Eduardo Bustamante
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=CAOSMAuvXZDpGOgr7W7Vx0ADWBHHYGoXSWRLaUPXUSG9pmO_7XQ@mail.gmail.com \
--to=dualbus@gmail.com \
--cc=p.w.stephenson@ntlworld.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).