🚀 go-pugleaf

In <1992Sep8.180216.3718@javelin.sim.es.com> rpack@javelin.sim.es.com (Rick Pack) writes:

>oneil@hns.com (Pat O'Neil) writes:

>>Anyone have any experience with the OS/2/2.0 Debug Kernel?  I have installed
>>it and can't get it to respond to an async terminal on COM1.  I've
>>read the directions pretty carefully and done everything they say, including:
>>
>>...... stuff deleted
>>
>>I would greatly appreciate any help.
>>
>>Pat O'Neil
>>Hughes Network Systems
>>Germantown, Md.

>  Pat,
>  I had terrible trouble with the debug kernel when I first tried to get
>it to work.  My system would crash after about 30 seconds of use.  Just
>getting it to boot was iffy.  I then started debugging with just printf
>statements, using the original kernal, figuring that the debugging kernal
>was buggy.
>  Just last week, I realized that the debugging kernal is NOT necessary, as
>there is a great debugger included in the c-set2 package that runs under
>PM and will debug PM programs.  It's called IPMD.  I STILL do not know
>what the purpose of the debugging kernal is, as IPMD works just fine without
>it, and there is none of this async terminal/serial port stuff.
>  The install documentation for workset/2 never mentions IPMD, just the debug
>kernal, which leads you to believe that it is your only option.

The debug kernel is needed for debugging device drivers or applications
that somehow cause a GP or page fault while the kernel is executing.

The PM debugger can only debug code that is running in ring 3.

-- 
Robert J. Olivier

rjo@panix.com