Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!mips!excelan!ames!amelia!izen
From: izen@amelia.nas.nasa.gov (Steven H. Izen)
Newsgroups: comp.unix.i386
Subject: Re: Kernel debugger
Message-ID: <4333@amelia.nas.nasa.gov>
Date: 22 Dec 89 06:00:21 GMT
References: <2640001@hpgnd.HP.COM> <64@zds-ux.UUCP>
Reply-To: izen@cwru.cwru.edu (Steven H. Izen)
Organization: Case Western Reserve University
Lines: 22

In article <64@zds-ux.UUCP> gerry@zds-ux.UUCP (Gerry Gleason) writes:
>In article <2640001@hpgnd.HP.COM> emmanuel@hpgnd.HP.COM (Emmanuel GAYET) writes:

>> I am looking for a kernel debugger for Unix System V/386 . I have heard that

>ISC's 386/ix has one that comes with their OS.  We use it quite a bit, and
>find it useful.  It's pretty basic, but has most of the features you really
>need.  Of course, if you already have another OS, and are looking for an
>add on package, this won't be much help.

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!  Every time I've entered
the debugger, either due to a panic, or by hitting ctrl-alt-d, the only way out
seemed to be the power switch.  Am I missing something?


-- 
Steve Izen: {sun,uunet}!cwjcc!skybridge!izen386!steve  / Quote corner:
or steve%izen386.uucp@skybridge.scl.cwru.edu          / 
or izen@cwru.cwru.edu	   /-------------------------/ My second bike is a car.
                           | The problem is that I *was* paying attention.