Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Strange coredump of zsh-3.0.2 (gcc optimizer/two different CPUs)
- X-seq: zsh-workers 2788
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: "C. v. Stuckrad" <stucki@xxxxxxxxxxxxxxxxx>, Zsh workers list <zsh-workers@xxxxxxxxxxxxxxx>
- Subject: Re: Strange coredump of zsh-3.0.2 (gcc optimizer/two different CPUs)
- Date: Mon, 13 Jan 1997 10:44:10 -0800
- In-reply-to: "C. v. Stuckrad" <stucki@xxxxxxxxxxxxxxxxx> "Strange coredump of zsh-3.0.2 (gcc optimizer/two different CPUs)" (Jan 13, 4:17pm)
- References: <Pine.GSO.3.95.970113152959.17033A-100000@petzval>
- Reply-to: schaefer@xxxxxxx
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author