Re: kernel module code coverage

From: Matthew Macy <mat.macy_at_gmail.com>
Date: Thu, 08 Aug 2019 19:04:43 -0000
The whole point of adding gcov support was for integrating with the
ZoL CI framework which does coverage. So it very much does work with
modules. Not sure where that comes from.
-M

On Thu, Aug 8, 2019 at 6:52 AM Alan Somers <asomers_at_freebsd.org> wrote:
>
> On Thu, Aug 8, 2019 at 7:42 AM Michael Tuexen <tuexen_at_freebsd.org> wrote:
> >
> >
> >
> > > On 8. Aug 2019, at 14:24, Slava Shwartsman <slavash_at_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
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
Received on Thu Aug 08 2019 - 17:04:43 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:22 UTC