Date: Wed, 6 Aug 2025 21:44:20 -0600 From: Warner Losh <imp@bsdimp.com> To: j_yoon.choi@samsung.com Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: How can I measure code coverage for a device driver? Message-ID: <CANCZdfrAa8Ogx4s3Wb0_YFR%2BKk=Fdf5kpMyGsLPA4xy4yiSPsw@mail.gmail.com> In-Reply-To: <20250807001811epcms2p247a7255786c41efb68fd20e7c8cc55fa@epcms2p2> References: <CGME20250807001811epcms2p247a7255786c41efb68fd20e7c8cc55fa@epcms2p2> <20250807001811epcms2p247a7255786c41efb68fd20e7c8cc55fa@epcms2p2>
next in thread | previous in thread | raw e-mail | index | archive | help
I think KCOV will work better than GCOV for this, but it's been a while since I've used either. Warner On Wed, Aug 6, 2025 at 6:19 PM Jaeyoon Choi <j_yoon.choi@samsung.com> wrote: > > Hi, > > I'd like to measure line/branch coverage while testing UFSHCI device driver > on FreeBSD. > Which tools or workflow do you recommend for collecting coverage data from > a device driver module? > > I've seen references to GCOV and KCOV, but I’m not sure which is the best fit > for a device driver scenario. > > Thanks in advance, > Jaeyoon Choi > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrAa8Ogx4s3Wb0_YFR%2BKk=Fdf5kpMyGsLPA4xy4yiSPsw>