Re: sparse triggers OOM killer

[Sam Ravnborg <sam@ravnborg.org>]

Hi Linus.

On Sat, Jan 07, 2006 at 10:07:10AM -0800, Linus Torvalds wrote:
> 
> 
> On Sat, 7 Jan 2006, Sam Ravnborg wrote:
> > 
> > There was no oops or similar and sparse just exited after a while with
> > an errorcode (137).
> 
> That's just SIGKILL (128+9). Which is normal for the OOM killer.
> 
> > Now I wonder if I have hit a bug in sparse or this is what I should
> > expect.
> 
> Well, sparse does keep a _lot_ of stuff in memory, and the "do many files 
> at once" will basically keep every single one (with full types, full 
> linearization etc) in memory at the same time.
> 
> It's probably fairly easy to fix: I should just make sparse release all 
> the linearizations and symbols when they go out of file scope.
> 
> The "do many files at once" thing really was just a quick hack, so the 
> lack of memory release is not that susprising.
> 
> I'll see what I can do.

Any news on this (call this a polite remineder)?
I have not tried to dig into it myself - assuming that it will take me
considerably time to do right..

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/