zsh-workers
 help / color / mirror / code / Atom feed
From: Erik Ogan <erik@ts2.galt.com>
To: zsh-workers@math.gatech.edu
Subject: zsh-2.5.03-2.6b17 under Solaris 2.5 trouble with mult()
Date: Tue, 07 May 1996 18:29:32 -0400	[thread overview]
Message-ID: <199605072229.SAA20258@ts2.galt.com.> (raw)

I just sub'ed yesterday, but I've poked around the archives and I
haven't found anything that seems even remotely related to this
problem.

The following occurs on all of our Solaris 2.5 boxes for zsh versions
2.5.03 - 2.6b17 (ok, I didn't try EVERY beta...:) but does NOT occur
under SunOS 4.1.x.

Everything compiles fine, but in the when it (gcc-2.7.2) tries to link:

gcc -o zsh builtin.o compat.o cond.o exec.o glob.o hashtable.o hist.o
init.o input.o jobs.o lex.o linklist.o loop.o math.o mem.o params.o
parse.o signals.o subst.o text.o utils.o watch.o zle_bindings.o
zle_hist.o zle_main.o zle_misc.o zle_move.o zle_refresh.o zle_tricky.o
zle_utils.o zle_vi.o zle_word.o -lnsl -ltermcap

generates the following warnings:

Warning: size of symbol `mult' changed from 4 to 284 in /lib/libmp.so.1
Warning: type of symbol `mult' changed from 1 to 2 in /lib/libmp.so.1

And the program will often dump core due to an illegal instruction
when searching command hash tables in a normal interactive incarnation
(works fine in a script, or in gdb (Yes, I know smart bugs can smell
programmer fear a mile a way)).

In light of that, the only other useful information I've found is by
doing a back trace on the core file in gdb. Doing so confirms that the
illegal instruction in question occurs in the mult() function, called
from the iscom() function (exec.c:388)

Being relatively new (read: forcibly dragged kicking and screaming) to
Solaris, I'm having some trouble with this, but under SunOS, (I would
assume its the same) this behavior would imply running out of memory,
or an illegal mult() operation.

The fact that I seem to be the only Solaris 2.5 user who's had this
problem disturbs me, and makes me look cross-eyed at our installation
of gcc.

Any ideas would be greatly appreciated, by me as well as my co-workers, 
most of whom are getting tired of listening to me swear up and down at 
tcsh.

--------
Erik R. Ogan
Webmaster/Systems Editor
GALT Technologies, Inc.



             reply	other threads:[~1996-05-07 22:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-07 22:29 Erik Ogan [this message]
1996-05-08  5:34 ` Clive Messer
1996-05-10 20:49 ` Zoltan Hidvegi

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=199605072229.SAA20258@ts2.galt.com. \
    --to=erik@ts2.galt.com \
    --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).