Re: flist -- "Killed" -- oom (*not* 1.8 related)

[Ken Hornstein]

>and, if not, any thoughts on how to debug?  if i build "cc -g", any
>thoughts on where to set breakpoints, or where to insert printf's, to
>try to track this down?

If you run under the debugger, you should stop when you receive the signal
from the OOM process.

That MIGHT be useful _if_ you hit the limit in the routine that is causing
the memory leak, which is likely but not guaranteed.  Otherwise you could
run under valgrind (it should be available in the packaging system for
your distro) which should very quickly tell you where memory is leaking.

--Ken