From: Johannes Findeisen <mailman@hanez.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] very mystic segmentation fault...
Date: Tue, 24 Dec 2002 14:59:46 +0100 [thread overview]
Message-ID: <200212241459.47102.mailman@hanez.org> (raw)
hi all,
first, i wish all gentoo developers a merry christmas. i don't need any gifts
this year because you have made it every day for me. i not only love gentoo
but the developers too... go on like this in the future!
now to my problem. i have since some weeks a problem on my production server.
everything worked great until some day i didn't remember. here is my harddisc
setup:
/dev/hda1 = /boot (for all distros installed)
/dev/hda2 = swap
/dev/hda3 = / (for my gcc 2.95.3 gentoo system)
/dev/hda5 = / (for my gcc 3.2 gentoo system)
/dev/hda6 = / (for any other gentoo system)
when i'm running the command
emerge rsync
the system segfaults at some point of syncinc the portage tree and when i'm
trying to compile something it's the same. but when i'm starting my gcc
2.95.3 system i have no problems at all. some weeks ago i thought it was a
memory problem because it only happens when i compiled glibc or some other
libs. i've started memtest but the memory is ok. then i tried to install a
new gentoo system on /dev/hda6 but when the bootstrap process began to
compile glibc the system segfaults again. i tried many other things but
without any luck.
yesterday i had another weired problem on this machine. i needed to shutdown
the system and when it starts again, many commands was not found anymore, so
the system started without the most services. i didn't changed anything for
some weeks in my system konfiguration or have installed any software.
i was going crazy because i really need this server for many things, so i
tried to make a chroot from my gcc 2.95.3 system to my gcc 3.2 system and do
an "emerge rsync". everything worked fine in the chrooted envoirenment. i
tried to compile glibc gcc and some other things and everything compiles
without any errors. after doing this i started my gcc 3.2 - now 3.2.1 because
i have updated it during the last merges in the chrooted envoirenment - and
it have booted up like there never have been any problems with it.
now i again wanted to try what happens when i run "emerge rsync" in this
system again. it segfaults at some point!!! i have tried to recompile glibc
or some other things and the same. it segfaults!!!
short again: i can compile in my gcc 2.95.3 system and in the chrooted
gcc 3.2.1 but only when i'm chrooting from my gcc 2.95.3 system. i defenitly
could not compile when the gcc 3.2.* system is runing.
could it be a problem with my /boot menu, because the installations are all
sharing one? every sys has its own kernel in there.
could it be a cpu problem? i'm compilling with these use-flags:
USE="-kde -qt -arts -qtmt -X -gtk -gnome -alsa -bonobo -evo -gb -gtkhtml
-motif -tcltk -svga -avi -mpeg -quicktime -esd -mikmod -oss -nas -ggi -dvd
-xmms -oggvorbis -flash -encode -ipv6 -spell -truetype -mozilla"
my processor is a celeron (coppermine) 630 mhz and this is my host setting:
CHOST="i686-pc-linux-gnu"
i don't know what to do with this problem. is the anybody outhere who has an
idea???
kind regards
hanez... ;-)
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2002-12-24 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 13:59 Johannes Findeisen [this message]
2002-12-27 19:27 ` [gentoo-dev] very mystic segmentation fault Evan Powers
2003-01-03 12:05 ` Johannes Findeisen
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=200212241459.47102.mailman@hanez.org \
--to=mailman@hanez.org \
--cc=gentoo-dev@gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox