Hi, I was debugging the OpenBSD kernel using Qemu and gdb. Well, it depends on the task. You can follow the below link if it suits to you and sees if it works for you.
http://bijanebrahimi.github.io/blog/remote-debugging-the-running-openbsd-kernel.html In my case, I was debugging pledge(2) and also trying to see what happens in the kernel when one invokes any userspace command like "ls" from the command line. I created a demo system call to use it in debugging. So, it was easy for me to track the flow from user-space to kernels. If you put a breakpoint on some other syscall then it will create a noisy output every time when kernel boots up and maybe kernel panics (if you use lots of prints) While in FreeBSD, I have used a ddb kernel debugger for bug related stuff. And yeah, I think you have to compile it every time if you make any changes to the source code and want to see the change. Regards, Neeraj On Wed, 30 Oct, 2019, 2:12 am List, <l...@md5collisions.eu> wrote: > Hi, > I was wondering how you guys debug your kernel? > Are you doing some vmd(8) voodoo ? > > Recompiling every time you think you've found the error gets quite > exhausting over time. > > g, > Stephan > >
