Date: Thu, 8 Aug 2019 17:16:58 +0300 From: Slava Shwartsman <slavash@FreeBSD.org> To: Alan Somers <asomers@freebsd.org>, Michael Tuexen <tuexen@freebsd.org> Cc: current <current@freebsd.org> Subject: Re: kernel module code coverage Message-ID: <bb5fa55b-7402-1f12-1c4b-2fdda962216f@FreeBSD.org> 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
On 08-Aug-19 16:52, Alan Somers wrote: > 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. >> Thanks. Is there a man page for /dev/kcov? >> 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. In worst case, I can build my module into the kernel, right? > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239194 > -Alan > Slava
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb5fa55b-7402-1f12-1c4b-2fdda962216f>