[MPlayer-users] segfault even when running with no input files or options

[Ron Johnson]

On 05/30/2012 10:44 PM, Lonni J Friedman wrote:
> On Wed, May 30, 2012 at 8:40 PM, Ron Johnson<ron.l.johnson at cox.net>  wrote:
>> On 05/30/2012 09:41 PM, Lonni J Friedman wrote:
>> [snip]
>>
>>> suppose that's possible, that seems unlikely when it also happens with
>>> a newly built mplayer binary too.
>>>
>>
>> Ah, I missed that part of your OP.
>>
>> I'm still puzzled as to why it seemingly just starting segfaulting out of
>> the blue.  Deterministic systems just don't do that.
>
> agreed, but i'm not sure how to debug this.

What causes programs to start segfaulting out of the blue without any 
other changes to the system?  H/w problems.

1) Memory corruption, but those are transient, causing whatever code 
that loads into that location to segfault.  Doesn't fit your symptoms.

2) Disk corruption.  That fits the repeatability symptom, but the fact 
that it still happens when you build from scratch means either that the 
issue is in a system file or you didn't first "make clean" (or whatever 
the mplayer build system calls it).

3) Controller corruption, which is highly unlikely unless your system 
was hit by a power surge, and then you'd see it in more than just one 
program.

-- 
"There is usually only a limited amount of damage that can be
done by dull or stupid people. For creating a truly monumental
disaster, you need people with high IQs."
Thomas Sowell