lkml.org 
[lkml]   [1996]   [Mar]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Kernel Compiling
Date


> To add to the din, Martin is correct. Corrupted/defective memory can
> easily lead to attempts to access stupid places in memory. If you have a
> valid pointer and it changes its value (for whatever reason), it no longer
> points to the same place. The point is not that sig 11 means bad memory,
> but that getting SEGV's while compiling the kernel is a good sign you have
> a memory problem. The same could be said of bus errors. (Last time I
> checked, neither gcc nor the kernel poked about in memory randomly:)

I didn't notice memory faults on my machine, however I get a sigsegv once
or twice when I compile a new kernel. This has happened with kernel post
3.64, before that I used 1.2.13 that worked fine and compiled ok.
Load average, before gcc dies with SIGSEGV is going sky-high, and problems
only arise when there is a memory shortage.

> K.

Matei


\
 
 \ /
  Last update: 2005-03-22 13:36    [W:0.029 / U:0.492 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site