segmantation fault error

[me-5yx05kfkO/aqeI1yJSURBw at public.gmane.org (Matthew Gillen)]

Kristian Hermansen wrote:
> On 7/9/07, Eugene Gorelik <eugene.gorelik-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
>> All memcheck test are passed.
> 
> Right, so it probably isn't a memory error.
> 
>> Yes it is not repeatable, when segfault happen it always points to
>> 0000000000000003 rip 0000003a9a970810.
>>
>> Ran gdb and analyzed core files and again all segfaults point to the same
>> memory address, seems like 100% physical memory issue.
> 
> So it is a bug in this once program.  But, I you should check out the
> stack trace in gdb with the 'bt' command.  It could very well be a zip
> bug, as I have reported many in zip, some on amd64.  

I find it hard to believe that a bad zip binary (even a malicious one) could
cause a kernel crash, unless it happens to be triggering a kernel bug.  But
then it would affect all his machines, and he said he had 29 good ones...

> If you are getting lots of segfaults in other programs, it could be
> possible that your libc has been corrupted. I would try something like
> this. Reinstall all the installed applications on the system. In 
> Debian/Ubuntu's APT, I would do this...
> 
> $ sudo aptitude reinstall ~i~Afeisty
> 
> There must be a similar command for yum, right?  Where are the yum
> experts?  That will ensure that you have replaced all the binaries on
> your disk with presumed good builds.  The above command says
> "reinstall all packages currently marked as installed in the feisty
> archive"...

Before you re-install anything, you can see if your binaries are modified by
verifying the md5sum of your binaries against the version from the installed
RPM with 'rpm -V zip' (if you see a '5' in the summary for a file, then it's
md5sum is different; there is no output at all if everything matches the RPM
db).  (note that if you do this for glibc, you'll need to be root to check one
of the files, you'll know you have permission issues if you see a '?')

Does it only happen with disk access?  If memory checks out, it might be a
faulty ide controller, or something else motherboard-related.

HTH,
Matt

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.