fatal signal 11

[Daniel Foesch]

>I started the compile again and it went past semaphore.c and died later on
>another file, started that make again and it continued. I then studied 'top'
>and saw the the machine was using virtually all its memory (I started this
>project on a machine with a modest 32meg or RAM). So, I got the cvs tree
>again on another machine with twice the memory and the compile completed
>successfully (albeit with warnings, but no fatal errors) and I can now run
>'wine calc.exe' from /c/windows. So, I will continue on for now. Thanks for
>the good advice. The searching (and reading the link) about sig 11 was
>interesting and useful and I appreciate it.
>
>>
>> BTW, does somebody know what could cause the sig11 in
>> wine/server/semaphore.c ?
>> Hmm, I guess I'll have to dig out some similar sig11 fixes and compare
>them
>> with semaphore.c content...
>>
>> Andreas Mohr
>>

I recall reading the Sig11 FAQ, and actually the way he's describing it (the
sig11 happens at arbitrary points in the compile) that means faulty mem sticks.

Daniel "Krach" Foesch
---------------------
"I'm all in favor of regulations dictating a standard placement of directions
on frozen foods" -Lyle McCracken