zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "C. v. Stuckrad" <stucki@math.fu-berlin.de>,
	Zsh workers list <zsh-workers@math.gatech.edu>
Subject: Re: Strange coredump of zsh-3.0.2 (gcc optimizer/two different CPUs)
Date: Mon, 13 Jan 1997 10:44:10 -0800	[thread overview]
Message-ID: <970113104410.ZM7791@candle.brasslantern.com> (raw)
In-Reply-To: "C. v. Stuckrad" <stucki@math.fu-berlin.de> "Strange coredump of zsh-3.0.2 (gcc optimizer/two different CPUs)" (Jan 13,  4:17pm)

On Jan 13,  4:17pm, C. v. Stuckrad wrote:
} Subject: Strange coredump of zsh-3.0.2 (gcc optimizer/two different CPUs)
}
} We had a case of very strange core dumps here:
} I compiled 3.0.2 with gcc 2.7.2 on a SUN Sparc10(sun4m) SunOS 4.1.3.
} This SUN exports all its Filesystems (except the root) to another
} 'sun4m' with a slightly different CPU (faster, more cache on chip).
} 
} On this 'second' machine contrary to the identical setup and type of
} machine this zsh coredumps during it's startup!
} 
} .................................................................
} Well, now I UN-Optimized 'mem.c', and (so far) the error was gone

Sounds like incompatible versions of dynamically-loaded libc, to me.
Are you sure that all the .so that zsh is loading are the same version
on both machines?

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern


  parent reply	other threads:[~1997-01-13 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-13 15:17 C. v. Stuckrad
1997-01-13 15:26 ` Strange coredump of zsh-3.0.2 (duplicated Lines, pleas excuse) C. v. Stuckrad
1997-01-13 18:44 ` Bart Schaefer [this message]
1997-01-14 11:20   ` Strange coredump of zsh-3.0.2 (gcc optimizer/two different CPUs) C. v. Stuckrad

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=970113104410.ZM7791@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=schaefer@nbn.com \
    --cc=stucki@math.fu-berlin.de \
    --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).