Date: Thu, 08 Aug 2019 12:41:10 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: slavash@FreeBSD.org Cc: current@freebsd.org Subject: Re: kernel module code coverage Message-ID: <15626.1565268070@critter.freebsd.dk> In-Reply-To: <b233b3e5-e2ac-8dce-5552-43bac9f8a5cc@FreeBSD.org> References: <b233b3e5-e2ac-8dce-5552-43bac9f8a5cc@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <b233b3e5-e2ac-8dce-5552-43bac9f8a5cc@FreeBSD.org>, Slava Shwar= tsman writes: >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? Back in early days, I fixed it so that all the BB-counter blocks in the kernel were linked into a list which could be read out through /dev/(k)mem, and I belive I added a program to do that, named something like "kernbb". Today I would probably have made a subtree under sysctl where the counters could be pulled out per source-file... -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15626.1565268070>