From: Hrvoje.Niksic@public.srce.hr (Hrvoje Niksic)
To: heading_anthony@jpmorgan.com (Anthony Heading)
Cc: zsh-workers@math.gatech.edu
Subject: Re: seg fault on $(dgqhghdqwdhqwjq) : beta19
Date: Sat, 25 May 1996 02:58:49 +0200 (MET DST) [thread overview]
Message-ID: <199605250058.CAA12532@jagor.srce.hr> (raw)
In-Reply-To: <199605242106.WAA24132@et-sun4.uk.jpmorgan.com> from Anthony Heading at "May 24, 96 10:06:40 pm"
In your mail, you said:
> Rather a large core file, but it takes no time to dump. So maybe
> it's not real. A peculiarity of SunOS 4.1.3?
I believe the size of the core file is a SunOS peculiarity (and I don't
think it's real either -- I used to ged "400M" core files without a
slightest change in df output).
As per the bug itself, I could not reproduce it on SunOS, but running a
non-existent command in backquotes returns me to the current directory (I
have autocd setopt-ed). I think this also counts as a bug. Oh, yes, I did
reproduce it on Linux, like:
Script started, file is typescript
gnjilux% setopt autocd
gnjilux% echo $ZSH_VERSION
2.6-beta19
gnjilux% pwd
/home/hniksic/work/zsh-2.6-beta19
gnjilux% $(obviously_not_in_path)
zsh: command not found: obviously_not_in_path
zsh: segmentation fault $(obviously_not_in_path)
gnjilux%
It is kernel 1.99.7.
--
hniksic@srce.hr | Student of electrical engineering
hniksic@fly.cc.fer.hr | University of Zagreb, Croatia
------------------------------------------------------------------
`VI' - An editor used by those heretics that don't subscribe to
the Emacs religion.
next prev parent reply other threads:[~1996-05-25 1:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-24 21:06 Anthony Heading
1996-05-25 0:58 ` Hrvoje Niksic [this message]
1996-05-27 1:13 ` Zoltan Hidvegi
1996-05-27 2:38 ` Thorsten Meinecke
1996-05-27 13:09 ` Zefram
1996-05-27 16:23 ` Thorsten Meinecke
1996-05-27 17:05 ` Zefram
1996-05-27 4:29 ` Richard Coleman
1996-05-27 17:02 ` 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=199605250058.CAA12532@jagor.srce.hr \
--to=hrvoje.niksic@public.srce.hr \
--cc=heading_anthony@jpmorgan.com \
--cc=hniksic@public.srce.hr \
--cc=zsh-workers@math.gatech.edu \
/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).