[Prev][Next][Index]
Re: FreeBSD kernel debugging (CPS210 course project)
- From: Jeff Chase <chase@cs.duke.edu>
- Newsgroups: duke.cs.cps210,duke.cs.os-research
- Subject: Re: FreeBSD kernel debugging (CPS210 course project)
- Date: Mon, 06 Apr 1998 11:25:53 -0400
- Organization: Duke University, Department of Computer Science
- References: <Pine.GSO.3.96.980402112640.6925A-100000@cetus.cs.duke.edu>
- CC: yhf, chase
- Xref: news.duke.edu duke.cs.cps210:143 duke.cs.os-research:185
Sorry for the delay on this. I forgot to click "send" on this last
week. I've edited a bit.
Haifeng Yu wrote:
>
> I have compiled the FreeBSD kernel and I get 3 executables (aicasm*,
> kernel*, genassym*) in my "sys/compile/CLUSTERBOX" directory. What are
> the executables for? How can I trace the kernel execution? I have not
> modified anything, so no rebooting is needed. What I want to do is to
> trace the kernel to see how it works.
>
Kernel is your bootable kernel image. The others are used in generating
the kernel. Basically, you install a kernel by placing it in the
appropriate place (preserving the old one), logging into the machine
with rconsole, and rebooting the machine.
There are detailed directions on the ari web (ari/local) for Digital
Unix systems, but we don't have local directions in place....though the
basic process (rconsole usage, etiquette, administrative commands) is
the same. There is detailed information on the freebsd web site (please
don't print it out), but they need to be augmented a bit with some local
rules. Drew is trying to gather this information in one place for us.
More on that later.
Tracing kernel execution is a little difficult. FreeBSD has an OK
kernel debugger, but it's really intended for postmortem debugging.
There's a remote debugger (teledebugger) but I don't think it will let
you do watchpoints, which is what you need to trace execution. Drew
knows more about this than anyone and he is back now, so he may be able
to add some information.
JC
Follow-Up(s):