Hello SuSE folkz, I'm completely puzzled... I'm getting total Segmentation Fault in SuSE9.2 If I run YaST in text mode or trying to execute make to compile some sources, it all crashes with seg fault message. Could somebody please enlighten me on this issue. Is it a SuSE kernel, deficiency in C libs or other things cause this problem? Thank you in advance for any help. Alex
On Tue, 1 Feb 2005, Alex Daniloff wrote:
Hello SuSE folkz, I'm completely puzzled... I'm getting total Segmentation Fault in SuSE9.2 If I run YaST in text mode or trying to execute make to compile some sources, it all crashes with seg fault message. Could somebody please enlighten me on this issue. Is it a SuSE kernel, deficiency in C libs or other things cause this problem? Thank you in advance for any help.
I'd guess Hardware. Run memtest86 or memtest86+. Otherwise, use rpm -V to verify the integrity of packages. You can use rpm -Va to verify all packages. There will always be configuration files and usually a few little issues but if anything from glibc or the kernel, etc... has been damaged this will tell you. I'd start with rpm -V glibc kernel-default etc... a few core packages, then memtest, then rpm -Va. -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <jnelson-suse@jamponi.net>
On Tuesday 01 February 2005 13:28, Alex Daniloff wrote:
Hello SuSE folkz, I'm completely puzzled... I'm getting total Segmentation Fault in SuSE9.2 If I run YaST in text mode or trying to execute make to compile some sources, it all crashes with seg fault message. Could somebody please enlighten me on this issue. Is it a SuSE kernel, deficiency in C libs or other things cause this problem? Thank you in advance for any help. Could be any of the above. You can try to run gdb on the core file, if there is one. Since you are doing things that many other people are doing routinely, I would possibly suspect some errors in installation of possibly bad memory.
To get a core dump, you need to set the corefile limit. Use the ulimit command: ulimit -c unlimited # This will set the core file limit to unlimited. ulimit -c 0 # This turns it off. So, set the limit to unlimited, and run something, like make. You can then run gdb. gdb /usr/bin/make core (gdb) r ... This will then tell you where the segfault is. It it is in a critical library, such as glibc, I would boot the installation, and reinstall. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
participants (3)
-
Alex Daniloff -
Jerry Feldman -
Jon Nelson