From: David Huggins-Daines <dhd@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] weird memory/file corruption errors building glibc and other things
Date: 18 Oct 2000 12:42:10 -0400 [thread overview]
Message-ID: <87wvf614pp.fsf@linuxcare.com> (raw)
Hi,
I get some very strange file corruption errors when building glibc on
the A180. Specifically the dependency files end up with weird garbage
overwritten in them, and the glibc build fails like this:
ln /home/build/glibc-2.1.95/hppa-linux/obj/dummy.d /home/build/glibc-2.1.95/hppa-linux/obj/stdlib/lshift.d
make[3]: @¸@¸/build/glibc-2.1.95/hppa-linux/obj/dummy.d: Command not found
make[2]: *** [stdlib/subdir_lib] Error 127
make[2]: Leaving directory `/home/build/glibc-2.1.95/glibc-2.1.95'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/build/glibc-2.1.95/hppa-linux/obj'
This seems to be mostly random, because if I remove the offending
files and restart the build, it will usually succeed.
I also get lots of other random errors when building other packages.
Usually these end up triggering assertions in bash's malloc wrapper
code or causing make to segfault or bus error. They are not
repeatable, and usually restarting the build makes them go away, at
least on the second or third try.
I don't know what other info I can provide. Like I say, the errors
are random and seem to be caused by memory corruption, though there
are a few places where they tend to get "caught" more often than not.
I am not using swap at all either, because swapping does not work - I
get "invalid swap entry" errors on the console and my processes
segfault or bus-error more quickly than usual.
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
reply other threads:[~2000-10-18 16:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87wvf614pp.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=parisc-linux@thepuffingroup.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.