Date: Thu, 8 Aug 2019 07:52:03 -0600 From: Alan Somers <asomers@freebsd.org> To: Michael Tuexen <tuexen@freebsd.org> Cc: "slavash@freebsd.org" <slavash@freebsd.org>, current <current@freebsd.org> Subject: Re: kernel module code coverage Message-ID: <CAOtMX2iv%2B_Q6kbOqUmcjpafoym0Yx9OU9p3LKt_mpYf7eEzrNw@mail.gmail.com> In-Reply-To: <C839BCA7-1FA9-4E0F-B03F-59B8E5FA6FFF@freebsd.org> References: <b233b3e5-e2ac-8dce-5552-43bac9f8a5cc@FreeBSD.org> <C839BCA7-1FA9-4E0F-B03F-59B8E5FA6FFF@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 8, 2019 at 7:42 AM Michael Tuexen <tuexen@freebsd.org> wrote: > > > > > On 8. Aug 2019, at 14:24, Slava Shwartsman <slavash@FreeBSD.org> wrote: > > > > Apparently, Bullseye are dropping support for FreeBSD. > > > > We are looking for an alternative for kernel module run time analysis. > > Mostly interested in code coverage (for now). > > > > Any suggestions that work for you? > Have you looked into /dev/kcov. This is used by SYZKALLER for getting > coverage information from the kernel. > > Best regards > Michael > > > > > > Slava That's part of Matt Macy's gcov project, right?. However, while it works for the kernel itself, it doesn't work for modules. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239194 -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2iv%2B_Q6kbOqUmcjpafoym0Yx9OU9p3LKt_mpYf7eEzrNw>