[gentoo-dev] very mystic segmentation fault...

[gentoo-dev] very mystic segmentation fault...

[Johannes Findeisen]

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

Re: [gentoo-dev] very mystic segmentation fault...

[Evan Powers]

On Tuesday 24 December 2002 08:59 am, Johannes Findeisen wrote:
> 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.

If you can compile when chrooting from 2.95.3 to the 3.2.1 system, but not 
when booting directly into the 3.2.1 system, my guess is that you have a 
kernel problem.

Theoretically, the only effective difference between the chroot environment 
and the directly booted environment is whether a 2.95.3 compiled or a 3.2.1 
compiled kernel is running.

Consider adding a new boot menu option which boots the gcc 3.2.1 system using 
the kernel from the 2.95.3 system. If you don't have problems with this, your 
3.2.1 system has a bad kernel.

WHY that kernel would be bad is a pretty open question. It probably has 
nothing to do with it being compiled with the newer gcc; perhaps the 
configuration is somehow wrong? Or perhaps Gentoo has started using newer 
kernel versions with slightly different binary interfaces, and you need to 
compile libc against the new kernel so that it uses the new binary interface.

Good luck, in any case.

Evan Powers


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] very mystic segmentation fault...

[Johannes Findeisen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hello evan,

thanks for your help. i reply to this message, to say that everything works 
fine now...

<snip>
> If you can compile when chrooting from 2.95.3 to the 3.2.1 system, but not
> when booting directly into the 3.2.1 system, my guess is that you have a
> kernel problem.
</snip>

i have started my gcc 2.95.3 system and have chrooted to my gcc 3.2.1. i have 
deleteted my old kernel wchich i used to start the gcc 3.2.1 system and have 
compiled a new one... i have copied the kernel config from my old system to 
the new and have compiled the new kernel. i have copied into my /boot 
directory and started the gcc 3.2.1 system again. and hep: everything works 
again.

i'm so happy, so i must say thank you evan. this was the best thing for me in 
the beginning of 2003. my server is lucky now an emerges what i want...

kind regards
johannes findeisen ... ;-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+FXyR1e37d/WNRDURAmQpAJ9fUEq0y2krbasMuqJ7M5uwJFsfQwCg3ZK9
hRyXTHvWBJcJPUmUehN+TaE=
=Ma6d
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list