Serious problem, something corrupt, help!
My system has suddenly started puking... it is running right
now, but limping... I have had similar problems before, and I
want to track this down.
grep dies with 'Aborted'
su and mount die with a segfault
Where should I start looking to track this? I changed nothing
on the system before this happened... I've been too busy to have
screwed it up.
last few lines of strace on grep
pipe([3, 4]) = 0
fork() = 18062
--- SIGCHLD (Child exited) @ 0 (0) ---
read(3, "\376", 1) = 1
brk(0) = 0x805aeb3
brk(0x807beb3) = 0x807beb3
brk(0) = 0x807beb3
brk(0x807c000) = 0x807c000
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
getpid() = 18061
kill(18061, SIGABRT) = 0
--- SIGABRT (Aborted) @ 0 (0) ---
+++ killed by SIGABRT +++
last 10 lines of strace on su
fstat64(3, {st_mode=S_IFREG|0644, st_size=3875, ...}) = 0
mmap2(NULL, 3875, PROT_READ, MAP_SHARED, 3, 0) = 0x40016000
_llseek(3, 3875, [3875], SEEK_SET) = 0
munmap(0x40016000, 3875) = 0
close(3) = 0
rt_sigaction(SIGINT, {SIG_IGN}, {SIG_DFL}, 8) = 0
time(NULL) = 1067873964
getuid32() = 50039
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
--
www.suave.net - Anthony Ball - ant@suave.net
Fill out a wishlist NOW for christmas www.suave.net/wl
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Any time, any place, our snipers can drop you. Have a nice day.
Reply to: