This is the mail archive of the
glibc-linux@ricardo.ecn.wfu.edu
mailing list for the glibc project.
Re: version woes
- To: glibc-linux at ricardo dot ecn dot wfu dot edu
- Subject: Re: version woes
- From: Kaz Kylheku <kaz at ashi dot footprints dot net>
- Date: Tue, 27 Jun 2000 04:00:11 -0700 (PDT)
- cc: Andreas Jaeger <aj at suse dot de>
- Reply-To: glibc-linux at ricardo dot ecn dot wfu dot edu
On Mon, 26 Jun 2000 eddy@eddy.casa-z.org wrote:
> Actually, I've gotten that problem before, and this is not the same thing.
> I think the one you're talking about came from having the wrong version of
> the linker, and would thus always happen. This only occurs spuriously, on
> commands that worked mere moments ago and that work again later, just not at
> the moment that I get the error.
>
> Do you have any other suggestions? I really appreciate your help.
Sounds like bad hardware. Why else would some non-real-time computation,
like executing a batch utility, behave differently on different invocations
with identical inputs?
Do you get random segfault when compiling a large program such as glibc, the
kernel or gcc?
http://www.bitwizard.nl/sig11/