Date: Thu, 5 Dec 2019 16:24:44 -0800 From: Matthew Macy <mmacy@freebsd.org> To: Ed Maste <emaste@freebsd.org> Cc: Alan Somers <asomers@freebsd.org>, Michael Tuexen <tuexen@freebsd.org>, "slavash@freebsd.org" <slavash@freebsd.org>, current <current@freebsd.org> Subject: Re: kernel module code coverage Message-ID: <CAPrugNojGqDYxL-kHiEGhn81XViAp_eA68kYbsPkpW1dn9Dv9g@mail.gmail.com> In-Reply-To: <CAPyFy2DSmW=eztZ5-HnynXDvrCuaHiJfTXZadyPDCQOFxumnMg@mail.gmail.com> References: <b233b3e5-e2ac-8dce-5552-43bac9f8a5cc@FreeBSD.org> <C839BCA7-1FA9-4E0F-B03F-59B8E5FA6FFF@freebsd.org> <CAOtMX2iv%2B_Q6kbOqUmcjpafoym0Yx9OU9p3LKt_mpYf7eEzrNw@mail.gmail.com> <CAPyFy2DSmW=eztZ5-HnynXDvrCuaHiJfTXZadyPDCQOFxumnMg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 5, 2019 at 8:38 AM Ed Maste <emaste@freebsd.org> wrote: > > > > Have you looked into /dev/kcov. This is used by SYZKALLER for getting > > > coverage information from the kernel. > > > > > That's part of Matt Macy's gcov project, right?. > > No, /dev/kcov is independent of, and predates, Matt Macy's work. It > provides broadly the same sort of information, but not using the same > interface. GCOV also depends on GCC - probably limiting its potential use cases largely to vendor CI.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPrugNojGqDYxL-kHiEGhn81XViAp_eA68kYbsPkpW1dn9Dv9g>