Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!bu-cs!mirror!ima!esegue!johnl
From: johnl@esegue.segue.boston.ma.us (John R. Levine)
Newsgroups: comp.unix.i386
Subject: Re: Kernel debugger
Message-ID: <1989Dec22.175755.5131@esegue.segue.boston.ma.us>
Date: 22 Dec 89 17:57:55 GMT
References: <2640001@hpgnd.HP.COM> <64@zds-ux.UUCP> <4333@amelia.nas.nasa.gov>
Reply-To: johnl@esegue.segue.boston.ma.us (John R. Levine)
Organization: Segue Software, Cambridge MA
Lines: 13

In article <4333@amelia.nas.nasa.gov> izen@cwru.cwru.edu (Steven H. Izen) writes:
>Maybe you can answer a question for me.  I've RTFMd and not been able to
>figure this one out.  TFM mentions setting breakpoints, but NOWHERE does it
>say how to start the kernel executingg again!

The trick here is reasoning by analogy:  What is the regular unix program the
most similar to the kernel debugger?  dc, of course.  How do you get out of
dc?  By typing ctrl/D.  (Only wimps type q.)  Case solved.  The manual could
be more helpful, although typing "help" to the debugger does tell you this.
-- 
John R. Levine, Segue Software, POB 349, Cambridge MA 02238, +1 617 864 9650
johnl@esegue.segue.boston.ma.us, {ima|lotus|spdcc}!esegue!johnl
"Now, we are all jelly doughnuts."