From: "Nadav Har'El" <nyh@math.technion.ac.il>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: Bug in zsh 3.0.8
Date: Wed, 13 Dec 2000 17:49:37 +0200 [thread overview]
Message-ID: <20001213174937.A23159@leeor.math.technion.ac.il> (raw)
In-Reply-To: <1001213153858.ZM11850@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Wed, Dec 13, 2000 at 03:38:58PM +0000
On Wed, Dec 13, 2000, Bart Schaefer wrote about "Re: Bug in zsh 3.0.8":
> On Dec 13, 4:14pm, Nadav Har'El wrote:
> }
> } /home/nyh$ cat /tmp/z.z
> } echo $ZSH_VERSION
> } let 'a[3]=2'
> } let 'a[3]=2'
> } /home/nyh$ zsh /tmp/z.z
> } 3.0.8
> } zsh: segmentation fault zsh /tmp/z.z
>
> I can't reproduce the crash here. Further, a[3] gets set to 2 for me.
>
> Does it happen to you with "zsh -f /tmp/z.z"? If not, we need to know
> what your startup files are changing.
It also happens with zsh -f. My system is Redhat 7.0, with the vanilla zsh:
/home/nyh$ uname -a
Linux tigger.haifa.radware.co.il 2.2.16-22 #2 Wed Oct 4 10:49:01 IDT 2000 i686 unknown
/home/nyh$ rpm -qf /bin/zsh
zsh-3.0.8-3
>
> Can you generate a stack trace, e.g. with gdb or dbx, and send it to us?
I'll try to compile zsh from sources to get a good stack-trace. So far I
only managed to get it from a non-stripped but non-"-g" binary I had lying
around, and got the following:
(gdb) r -f /tmp/z.z
Starting program: /usr/local/bin/zsh -f /tmp/z.z
3.0.8
Program received signal SIGSEGV, Segmentation fault.
0x806e0a5 in setiparam ()
(gdb) where
#0 0x806e0a5 in setiparam ()
#1 0x806a05d in setvar ()
#2 0x806b45f in op ()
#3 0x806b95f in mathparse ()
#4 0x806b60d in mathevall ()
#5 0x806b72f in matheval ()
#6 0x8054129 in bin_let ()
#7 0x804aa23 in execbuiltin ()
#8 0x80588a5 in execcmd ()
#9 0x8056930 in execpline2 ()
#10 0x80560d6 in execpline ()
#11 0x8055d33 in execlist ()
#12 0x8062f6c in loop ()
#13 0x8062ddc in main ()
#14 0x4005ae51 in __libc_start_main (main=0x8062cc0 <main>, argc=3,
ubp_av=0xbffffa44, init=0x8049ad4 <_init>, fini=0x809014c <_fini>,
rtld_fini=0x4000e264 <_dl_fini>, stack_end=0xbffffa3c)
at ../sysdeps/generic/libc-start.c:111
If this is not enough information, I can compile it again with -g and
send you more information (and/or try to debug it myself).
Thanks!
Nadav.
--
Nadav Har'El | Wednesday, Dec 13 2000, 16 Kislev 5761
nyh@math.technion.ac.il |-----------------------------------------
Phone: +972-53-245868, ICQ 13349191 |Computers are like air conditioners.
http://nadav.harel.org.il |Both stop working if you open windows.
next prev parent reply other threads:[~2000-12-13 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 14:14 Nadav Har'El
2000-12-13 15:38 ` Bart Schaefer
2000-12-13 15:49 ` Nadav Har'El [this message]
2000-12-13 15:46 ` Bart Schaefer
2000-12-13 15:52 ` Nadav Har'El
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=20001213174937.A23159@leeor.math.technion.ac.il \
--to=nyh@math.technion.ac.il \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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).