On Fri, May 4, 2018 at 12:12 PM, andrey mirtchovski
wrote:
> It is unfortunately not reproducible. I got 2 crashes out of 500
> million executions. I've updated to tip and have not seen it since.
It is possible that it has been fixed on tip. There have been fixes
in the right areas, such as http
It is unfortunately not reproducible. I got 2 crashes out of 500
million executions. I've updated to tip and have not seen it since.
On Fri, May 4, 2018 at 12:14 PM, Ian Lance Taylor wrote:
> On Thu, May 3, 2018 at 11:39 PM, andrey mirtchovski
> wrote:
>>
>> I believe I've never encountered this
On Thu, May 3, 2018 at 11:39 PM, andrey mirtchovski
wrote:
>
> I believe I've never encountered this nor seen anyone mention this
> error before. It occurred while fuzzing a C library that we interface
> with:
>
> PC=0x7fffbafc847c m=0 sigcode=0
>
> goroutine 0 [idle]:
> runtime: unknown pc 0x7fff
