On Wed, Oct 17, 2018 at 9:40 PM, Greg Steuck wrote:
> On Wed, Oct 17, 2018 at 12:00 PM Dmitry Vyukov wrote:
>>
>> On Wed, Oct 17, 2018 at 4:50 AM, Greg Steuck wrote:
>> > I think I see some evidence of occasional VM just never finishing
>> > booting to
>>
recv: progs 0,
> repros 0; more 0
> 2018/10/16 19:35:28 VMs 2, executed 68406, cover 18582, crashes 78, repro 0
> 2018/10/16 19:35:38 VMs 2, executed 68451, cover 18582, crashes 78, repro 0
> 2018/10/16 19:35:48 VMs 2, executed 68479, cover 18582, crashes 78, repro 0
> 2018/10/16 19:35:
On Tue, Oct 2, 2018 at 8:02 PM, Greg Steuck wrote:
> Dmitry, is there an easy way get at the VMs output?
You mean the test VM instances (vmd), right?
We capture vmm/kernel output for crashes, you can see it in the Log
columns for each crash here:
https://syzkaller.appspot.com/#openbsd
Also if
On Mon, May 1, 2017 at 12:28 PM, Mark Kettenis wrote:
>> From: Dmitry Vyukov
>> Date: Mon, 1 May 2017 10:43:26 +0200
>>
>> On Mon, May 1, 2017 at 8:51 AM, Greg Steuck wrote:
>> > I naively tried to build something with -fsanitize=address using llvm-4.0
>>
On Mon, May 1, 2017 at 8:51 AM, Greg Steuck wrote:
> I naively tried to build something with -fsanitize=address using llvm-4.0
> port available on OpenBSD 6.1-amd64. I was immediately greeted with:
> clang-4.0: error: unsupported option '-fsanitize=address' for target
> 'amd64-unknown-openbsd6
