This morning on my computer I found:
Stack segment:
CPU:0
EIP:0010[<3451>]
EFLAGS:00010246
eax:2000 ebx: ecx: edx:00012000
esi:0001 edi:01606e08 ebp:0003 esp:01606db0
ds:0018 es:0018 fs:0026 gs:0026 ss:0018
Process Savelog(pid:2842, prcess nr: 24,stackpage=0160
Few month a go I had the same problem (sigsegv in gcc), solved it by
changing the motherboard. I suspect it was the cache but I can't say
for sure.
Hope that helps,
borik
---
Boris D. Beletsky [EMAIL PROTECTED]
Syst
On Thu, 24 Apr 1997, Felix Almeida wrote:
> On Wed, 23 Apr 1997, John Maheu wrote:
>
> > Hi all: I'm fairly new to linux. Lately I've been getting a lot of fatal
> > signal 11's.
>
> > gcc: Internal compiler error: program f771 got fatal signal 11
>
> This error means a problem with your me
On Wed, 23 Apr 1997, John Maheu wrote:
> Hi all: I'm fairly new to linux. Lately I've been getting a lot of fatal
> signal 11's.
> gcc: Internal compiler error: program f771 got fatal signal 11
This error means a problem with your memory or with your cache (try to
look the GCC FAQ). You can
> "John" == John Maheu <[EMAIL PROTECTED]> writes:
John> Hi all: I'm fairly new to linux. Lately I've been getting a
John> lot of fatal signal 11's.
John> It seems to occur when my system has been up for a few days
John> under light load or up a day under a heavier load, runni
There's something in the kernel 2.0 readme about this problem. It is
related to hardware problems. For me, it turned out to be a problem with
the external cache in my motherboard.
Al Youngwerth
[EMAIL PROTECTED]
--
> From: John Maheu <[EMAIL PROTECTED]>
> To: debian-user@lists.debian.org
6 matches
Mail list logo
