Date: Thu, 5 Dec 2019 07:52:17 -0500 From: Ed Maste <emaste@freebsd.org> To: Alan Somers <asomers@freebsd.org> Cc: Michael Tuexen <tuexen@freebsd.org>, "slavash@freebsd.org" <slavash@freebsd.org>, current <current@freebsd.org> Subject: Re: kernel module code coverage Message-ID: <CAPyFy2DSmW=eztZ5-HnynXDvrCuaHiJfTXZadyPDCQOFxumnMg@mail.gmail.com> In-Reply-To: <CAOtMX2iv%2B_Q6kbOqUmcjpafoym0Yx9OU9p3LKt_mpYf7eEzrNw@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>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2DSmW=eztZ5-HnynXDvrCuaHiJfTXZadyPDCQOFxumnMg>