Issues discovered by fuzzing

[nemequ]

I know you're working on the issues I e-mailed you about a while back; I'm just opening this to track the issue so I have something to link to on https://github.com/nemequ/compfuzz/wiki/Results.

They were reported on 2015-10-04, so they will be made public on 2016-04-04 or when they are fixed, whichever comes first (see https://github.com/nemequ/compfuzz#disclosure-policy).

[nemequ]

I haven't verified it yet, but should be fixed by 3f0b586.

[nemequ]

It looks like a lot of these still aren't fixed. Have you tried running them with AddressSanitizer or valgrind?

[fusiyuan2010]

I went through last batch of failed files and fixed them. I will check
again and hopefully fix it within this week.

Sorry for this and thanks for reporting

Siyuan
On Jan 5, 2016 9:56 PM, "Evan Nemerson" notifications@github.com wrote:

Reopened #7 #7.

—
Reply to this email directly or view it on GitHub
#7 (comment).

[nemequ]

NP, thanks for fixing them. I'll send you an updated archive tomorrow with a bunch of new files.

[nemequ]

Sorry, I just realized the files I tested were from a set I hadn't sent you. The archive I sent you this morning is more complete, from a new run last night.