manager crashes on accessing /cover about syzkaller HOT 7 CLOSED

Is there any error message after manager?

from syzkaller.

Not at all, it's like this:
syzkaller> syz-manager -config syzkaller.cfg
2016/02/16 11:21:59 loading corpus...
2016/02/16 11:22:01 loaded 1472 programs
2016/02/16 11:22:01 serving http on http://0.0.0.0:56741
2016/02/16 11:22:01 serving rpc on tcp://127.0.0.1:52034
syzkaller>

I.e. a prompt is shown.

from syzkaller.

Hummm... Can it be an OOM kill? Memory consumption can grow significantly when coverage report is requested.

from syzkaller.

Nope, dmesg is clean. No trace of OOM killer, neither crashes. I ran manager insider gdb, but cannot reproduce yet.

from syzkaller.

Humm... I am out of ideas. Go programs don't exit silently until you say os.Exit (which I don't as far as I see).

If gdb won't show anything useful, let's try to fix profile generation first. Maybe the crash will go away if we fix that...

from syzkaller.

it didn't happen with gdb. Neither it happens w/ debuginfo.

from syzkaller.

OK, I am going to close this. It is not actionable and harmless provided that I add proper diagnosis for missed debug info. Feel free to reopen if you localize the root cause.

from syzkaller.