From: Adam Spiers <adam@spiers.net>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: core dump with fc
Date: Tue, 11 Apr 2000 21:38:23 +0100 [thread overview]
Message-ID: <20000411213823.B1605@thelonious.new.ox.ac.uk> (raw)
I have an alias for extracting from tar balls after looking at them
(thanks Bart :-)
xt: aliased to fc -e - tvf=xf ztf=zxf -1
However ...
$ echo tvf
$ xt
zsh: 15486 segmentation fault (core dumped) zsh
Stack trace follows. This /doesn't/ happen if I start up with -f, but
I'm hoping the bug is obvious enough that I won't have to narrow the
problem down to one particular line in my huge .zshrc.
#0 0x80542a3 in fcsubs (sp=0xbffff43c, sub=0x646c6f62) at builtin.c:1345
1345 oldstr = sub->name;
#1 0x805452c in fclist (f=0x80e2b20, n=0, r=0, D=0, d=0, first=3039,
last=3039, subs=0x40014a88, pprog=0x0) at builtin.c:1410
#2 0x805410f in bin_fc (nam=0x40014a38 "fc", argv=0xbffff4c8,
ops=0xbffff51c "", func=16) at builtin.c:1279
#3 0x8052047 in execbuiltin (args=0x400149e8, bn=0x80b37bc) at builtin.c:368
#4 0x8062497 in execcmd (state=0xbffff7c8, input=0, output=0, how=18, last1=2)
at exec.c:2254
#5 0x805f18e in execpline2 (state=0xbffff7c8, pcode=323, how=18, input=0,
output=0, last1=0) at exec.c:1180
#6 0x805e70d in execpline (state=0xbffff7c8, slcode=8194, how=18, last1=0)
at exec.c:973
#7 0x805e129 in execlist (state=0xbffff7c8, dont_change_job=0, exiting=0)
at exec.c:820
#8 0x805de37 in execode (p=0x40014960, dont_change_job=0, exiting=0)
at exec.c:726
#9 0x80725e3 in loop (toplevel=1, justonce=0) at init.c:150
#10 0x805164c in main (argc=1, argv=0xbffff874) at ./main.c:86
#11 0x4006acb3 in __libc_start_main (main=0x8051470 <main>, argc=1,
argv=0xbffff874, init=0x8050a00 <_init>, fini=0x80ab42c <_fini>,
rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffff86c)
at ../sysdeps/generic/libc-start.c:78
next reply other threads:[~2000-04-11 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 20:38 Adam Spiers [this message]
2000-04-11 21:56 ` Bart Schaefer
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=20000411213823.B1605@thelonious.new.ox.ac.uk \
--to=adam@spiers.net \
--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).