kernel module code coverage
Alan Somers
asomers at freebsd.org
Thu Aug 8 19:08:09 UTC 2019
Read the bug report. I can't even load modules when I build with GCOV.
On Thu, Aug 8, 2019 at 1:04 PM Matthew Macy <mat.macy at gmail.com> wrote:
>
> 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"
More information about the freebsd-current
mailing list