I doubt anyone here is super-jazzed to add golang to the NMH codebase, but
this looked interesting:
https://proton.me/blog/gluon-imap-library
Roughly, the Proton Mail people build a library to handle some of the same
sorts of IMAP problems that nmh conceptually has.
If that's not interesting,
>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
hi.
for some years now, i occasionally get in a situation where flist
gobbles up lots of memory, and is then killed by the kernel's "oom"
procedure. eventually this goes away, though i'm not exactly sure how
that happens either.
bash archlinux (master): {50071} flist -sequence unseen -all
