Dmitry Vyukov

> (my lack of experience in Golang might play role in this). > > I think we should improve syz-bisect interface instead. I don't see this providing significant additional value...

Hi Christoph, How frequently/soon does it crash? I don't remember seeing anything similar on syzbot nor locally. Do you have any local modifications? What syzkaller commit are you using? Recently...

We do this trick to dump more info when decoding programs: https://github.com/google/syzkaller/blob/master/prog/encoding.go#L252-L257 But it won't work for encoding, since if encoding panics we cannot encode to dump it :) Maybe...

What's in the crash log files for these? They should contain unmasked values for these NUM/ADDR + maybe some additional info (stack, programs).

It also may be some bad programs in the corpus.

> Yes, let's create a separate issue for that. To not let it stop debugging of the original problem, does it work if you remove the following line and recompile...

> Then again, 6 minutes later I get the backtrace from the top of this issue, though I've been running with the `debug` config as suggested. What would we expect...

We could diverge from that rule for a short period of time. Nobody really asked us for 2 versions. Just spotted this: https://twitter.com/val_deleplace/status/1787818710822011163

We discussed this within the team and it sounds good. Please also add docs/translations/README.md similar to https://docs.kernel.org/translations/index.html But we need something shorter, I think we can start with just: ```...

It looks like a single goroutine can't keep up pregenerating inputs:  I think we need to start NumCPU goroutines + pre-serialize programs in Requests, so that Exchange can just...