Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
Due to network maintenance being performed by our provider, LQ will be down starting at 05:01 AM UTC. The exact duration of the downtime isn't currently known. We apologize for the inconvenience.
|
 |
07-20-2005, 11:54 AM
|
#1
|
|
Member
Registered: Mar 2002
Location: Sweden
Distribution: Slackware 10.1
Posts: 103
Rep:
|
Segmentation fault, WHY??
After rebooting my computer I now get this all the time.
root@silverserver:/# ls
Segmentation fault
root@silverserver:/# ls -l
Segmentation fault
root@silverserver:/# ls -a
Segmentation fault
root@silverserver:/# dir
Segmentation fault
root@silverserver:/#
I can allso se that when I boot linux up there are some errors with mysql and some more program and they all has Segmentation fault in the error line. Plz help me.
|
|
|
|
07-20-2005, 12:04 PM
|
#2
|
|
Senior Member
Registered: Mar 2004
Distribution: Slackware
Posts: 4,282
Rep:
|
You're out of luck
Try to boot from a slackware CD (1 or 2)
mount your system partition in /mnt/hd
chroot /mnt/hd
rm /lib/libc.so.6
ln -s /lib/libc-2.3.4.so /lib/libc.so.6
remove the CD and reboot
|
|
|
|
07-20-2005, 12:10 PM
|
#3
|
|
Member
Registered: Mar 2002
Location: Sweden
Distribution: Slackware 10.1
Posts: 103
Original Poster
Rep:
|
Humf, then I have to download the cd beacuse I don't have them
Do you know why?
|
|
|
|
07-20-2005, 12:12 PM
|
#4
|
|
Senior Member
Registered: Mar 2004
Distribution: Slackware
Posts: 4,282
Rep:
|
Maybe you can do it without boot from CD (as you are here)
Do the ln and rm commands work ?
As for why, I had exactly the same problem after a bad glibc upgrade
|
|
|
|
07-20-2005, 12:13 PM
|
#5
|
|
Member
Registered: Mar 2002
Location: Sweden
Distribution: Slackware 10.1
Posts: 103
Original Poster
Rep:
|
yes, it looks like that!!
edit....
Now I have destroyed it totaly  Now I can't start it at al. How should I do to fix it from my slackware cd (downloading it at the moment). I think I have to install the glibc files again to.
hmm.
chroot /mnt/hd and i get Segmentation fault. What to do??
Last edited by eXor; 07-20-2005 at 12:49 PM.
|
|
|
|
07-20-2005, 12:56 PM
|
#6
|
|
Moderator
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,505
Rep: 
|
You might want to run a 'memtest86' on your memory. Other than that, you don't HAVE to chroot to execute those commands.
|
|
|
|
07-20-2005, 01:06 PM
|
#7
|
|
Member
Registered: Mar 2002
Location: Sweden
Distribution: Slackware 10.1
Posts: 103
Original Poster
Rep:
|
Now I think I have succeced to fix so that I can go in to the orginal kernel.
Hmm, maybe glibc-2.3.5-i486-2 is rotten!!! I will try to go back to 2.3.4 beacuse there are several other programs that has crash and all has somthing to do with glibc.
Now I'm back with only having the glibc problem not Segment problem so thx for helping me with that.
|
|
|
|
07-20-2005, 01:30 PM
|
#8
|
|
Senior Member
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721
Rep:
|
|
|
|
|
07-20-2005, 01:55 PM
|
#9
|
|
Member
Registered: Mar 2002
Location: Sweden
Distribution: Slackware 10.1
Posts: 103
Original Poster
Rep:
|
I have succeded to install glibc-2.3.5 again and my system is runnig but with all the errors I had at the beging.
Maybe glibc-2.3.5 is bad.
Get's error like this one
*** glibc detected *** double free or corruption (!prev): 0x082c1ed0 ***
[Wed Jul 20 20:54:30 2005] [notice] child pid 17587 exit signal Abort (6)
-----extra-----
I followed your guide and remove all with 2.3.5 and installed 2.3.4 and now everything seems to work.
Wonder wy 2.3.5 was so bad
-----sadly-----
I still get this error on my apache server
[Wed Jul 20 21:27:27 2005] [notice] child pid 1434 exit signal Abort (6)
*** glibc detected *** double free or corruption (!prev): 0x082c0fc0 ***
[Wed Jul 20 21:31:12 2005] [notice] child pid 1589 exit signal Abort (6)
[Wed Jul 20 21:31:50 2005] [notice] child pid 1432 exit signal Segmentation fault (11)
*** glibc detected *** double free or corruption (!prev): 0x082c1120 ***
[Wed Jul 20 21:32:05 2005] [notice] child pid 1591 exit signal Abort (6)
Last edited by eXor; 07-20-2005 at 02:34 PM.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 09:34 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|