From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3595 invoked from network); 13 Jan 1997 18:40:07 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by coral.primenet.com.au with SMTP; 13 Jan 1997 18:40:07 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id NAA26731; Mon, 13 Jan 1997 13:38:07 -0500 (EST) Resent-Date: Mon, 13 Jan 1997 13:38:07 -0500 (EST) From: "Bart Schaefer" Message-Id: <970113104410.ZM7791@candle.brasslantern.com> Date: Mon, 13 Jan 1997 10:44:10 -0800 In-Reply-To: "C. v. Stuckrad" "Strange coredump of zsh-3.0.2 (gcc optimizer/two different CPUs)" (Jan 13, 4:17pm) References: Reply-To: schaefer@nbn.com X-Mailer: Z-Mail (4.0b.820 20aug96) To: "C. v. Stuckrad" , Zsh workers list Subject: Re: Strange coredump of zsh-3.0.2 (gcc optimizer/two different CPUs) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"HIAK8.0.ZX6.E4eso"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2788 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu 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