On Tue, Sep 09, 2003 at 07:41:50AM -0700, Hugo Vanwoerkom wrote:
> I always thought a sig 11 was hardware caused:
A signal 11 (segmentation fault) means that the program accessed memory
outside its permitted range. Occasionally this is caused by bad
hardware, but it's also frequently caused by bug
I always thought a sig 11 was hardware caused:
overheating of the cpu, until...
I installed MPlayer and it ALWAYS gets sig 11's on my
machine and tasks that REALLY use the cpu, like a 3
hour Mozilla compile, NEVER get sig 11's. The only sig
11 my machine ever sees is the one by MPlayer.
So may be i
On Tue, 09 Sep 2003 05:00:15 +0200, Bradley Alexander wrote:
> I've been seeing problems for the past several weeks and I am finally
> beginning to see a pattern. It started about the time I upgraded to a
> GeForce4MX after my GeForce2 died. At first I thought it was being
> caused by Gnome apps,
Bradley Alexander <[EMAIL PROTECTED]> writes:
> I've been seeing problems for the past several weeks and I am finally
> beginning to see a pattern. It started about the time I upgraded to a
> GeForce4MX after my GeForce2 died. At first I thought it was being caused
> by Gnome apps, because it was
I've been seeing problems for the past several weeks and I am finally
beginning to see a pattern. It started about the time I upgraded to a
GeForce4MX after my GeForce2 died. At first I thought it was being caused
by Gnome apps, because it was happening with greater frequency with Galeon
and Evolut
5 matches
Mail list logo
