I've had segment faults before that were
caused by faulty memory - my suggestion
would be to run a memory check
It may not be the problem - but it is easy
to check
e.g. memtest86 - includes a zip to create
a boot floppy - I keep the floppy handly
so I can check memory when strange things
happen - I have a few old servers :-)
-Cheers
-Andrew
--
MS ... if only he hadn't been hang gliding!
> Strange situation. I recently did a clean install of 7.1 on my previous
> 7.0 system from purchased RedHat CDs.
>
> When I do a rpm -qa, it shows all the installed packages up to
> StarOffice-5.2_34_569a20-2
> Then Segmentation fault.
> I have done this:
> rpm -e StarOffice
> It removed it and gave no errors.
> rpm -qa
> Same result, Seg fault after StarOffice-5.2_34_569a20-2
> rpm -q StarOffice
> it reports it is not installed.
> rpm --rebuilddb
> Seg faults
> Using the same CD, I have done
> rpm -i --force rpm-4.0.2-8
>
> it installed again, no errors, but trying all the above results
> in Seg Fault.
>
> Also running up2date results in a python crash error shortly after the
> progress window of retrieving list of files.
>
> doing a file on core, reports
> core: ELF 32-bit LSB core file of 'rpmq' (signal 11), Intel 80386,
> version 1, from 'rpmq'
>
> --
> Ray Atnip
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
