You are not logged in.
Hi people!
I'm configuring Arch after I installed it, but that's not my main problem.
I'm experiencing segmentation faults.
Yesterday I updated my system, just after I installed it, with pacman -Syu;
I'm installing ALSA like the wiki tells me. But when I ran alsamixer I get a segmentation fault.
So I thought, bad luck, maybe it's just ALSA and I installed something very mainstream: Lynx, but when I ran lynx I got a segmentation fault too!
How is it possible that everything I install gives segmentation faults? My RAM is not broken because I can use livecd's who are fully using my RAM with no problem;
Is it a userrightsproblem? And how to fix it?
Laurent
#Marked thread as solved
Last edited by Laurent (2009-02-10 21:21:00)
Offline
On top of what pyther asked, you may also want to try a stace trace or gdb to see if the segfaults are happening in the same library.
Offline
I have an AMD Athlon 64 3000+, never clocked it in any way
I don't think my hard drive is bad, I have two hard drives in raid1, one is about 5 years old, the other is 1 month old....
dmesg showed indeed something but I didn't understand a thing of it. (I'll search for it, I must reboot, my livecd won't mount them)
It's also strange that only programs installed after my system was installed (and thus after pacman -Syu) show segfaults.
Should I roll back my pacman? Maybe my kernel compiled not that right. I read something on the internet about a bad glibc, is that possible?
Sorry I'm a bit n00by, but I never experienced segfaults before
Offline
glibc was one of the libraries that I was thinking that gdb may expose. You can still run pacman right? If so, try and force reinstall glib with pacman -Sf glibc.
Offline
Sorry, it was not in dmesg.log but in messages.log I saw an error.
When I ran lynx I got a segmentation fault which messages.log confirmed
Feb 9 22:45:03 apollo lynx[3362]: segfault at 400000 ip 7f46eb456f48 libc-2.8.so[7f46eb3f2000+14a000+]
So libc is the evil. I'll try to reinstall it tomorow, it's to late now.... *need sleep*
Thanks for the help
A last question: Why can't fstab mount partitions with an ' in the name (e.g. /home/laurent/Afbeeldingen/Foto's), even when I escape them with a backslash?
EDIT: lots of typo's discovered, it's late, yes
Last edited by Laurent (2009-02-09 22:02:55)
Offline
Try using quotes instead.
Offline
The fstab solution was just using the ascii codes for a single quote (\047).
(g)libc is still the evil. Now it is version 2.9 instead of version 2.8 after a pacman update.
And pacman -Sf glibc gives no difference, I still get segmentation faults.
How is that possible?
Offline
You're segfault posted above was for glibc-2.8, and as you pointed out Arch is at 2.9 now. Is your system fully up to date as of today?
Offline
Fully up to date, yesterday it was fully up to date too!
It seems strange to me
EDIt: Solved!
I saw that the Belgium mirror was three days out of sync, so I switched to the French mirrors and ran a pacman -Syu, now, everything is just fine
Last edited by Laurent (2009-02-10 21:18:57)
Offline
Sweet!
Offline
***I removed the spam because I agree with that it's garbage. Thank you clickit -- skottish***
garbages !!!!
Offline
***link removed by skottish***
garbages !!!!
No worries. He/She/It is done.
Offline
hello skottish, grabage link removal is partial and still there in the clickit code box :-)
Offline
hello skottish, grabage link removal is partial and still there in the clickit code box :-)
Thanks. I'm suffering from pre-caffeine syndrome. I'm getting better now.
Offline