From: Clint Adams <clint@zsh.org>
To: nce@SLAC.Stanford.EDU
Cc: zsh-workers@sunsite.dk
Subject: Re: 64-bit sparc instructions
Date: Thu, 24 May 2001 00:49:26 -0400 [thread overview]
Message-ID: <20010524004926.A10577@dman.com> (raw)
In-Reply-To: <20010523192407.D9730@flora01.SLAC.Stanford.EDU>; from nce@SLAC.Stanford.EDU on Wed, May 23, 2001 at 07:24:08PM -0700
> I'd been thinking the cause of the trouble was equally probable between
> the compiler and the 64-bit libraries, but it seems you've eliminated
> both. Does echo =(echo foo) crash the gcc executable as well?
% Src/zsh -f
% echo =(echo foo)
/tmp/zshYdd7uR
% exit
% file Src/zsh
Src/zsh: ELF 64-bit MSB executable, SPARC V9, version 1, statically linked, not stripped
The above machine is a Sun Blade 1000 running Debian. The binary was
compiled with the prerelease gcc.
% Src/zsh -f
zsh: failed to load module: zsh/zle
% echo =(echo foo)
zsh: segmentation fault (core dumped) Src/zsh -f
% file Src/zsh
Src/zsh: ELF 64-bit MSB executable SPARCV9 Version 1, UltraSPARC1 Extensions Required, dynamically linked, stripped
The above machine is an Ultra 80 running Solaris 8. The binary was
compiled with Forte C. I'll see about getting the same version of gcc on
that box to provide a better comparison.
next prev parent reply other threads:[~2001-05-24 4:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 2:24 nce
2001-05-24 4:49 ` Clint Adams [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-23 3:04 vi editting troubles Paul Ackersviller
2001-05-23 4:41 ` 64-bit sparc instructions Bart Schaefer
2001-05-23 9:38 ` Andrej Borsenkow
2001-05-23 16:42 ` Clint Adams
2001-05-23 12:29 ` Clint Adams
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=20010524004926.A10577@dman.com \
--to=clint@zsh.org \
--cc=nce@SLAC.Stanford.EDU \
--cc=zsh-workers@sunsite.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).