Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!jwt!john
From: john@jwt.UUCP (John Temples)
Newsgroups: comp.unix.sysv386
Subject: Re: Kernel core dumps (was Re: out of swap space??)
Keywords: forced panic
Message-ID: <7!P+YND@jwt.UUCP>
Date: 14 May 91 02:50:29 GMT
References: <9105122137.aa00923@art-sy.detroit.mi.us> <1991May13.162909.20686@turnkey.tcc.com> <1991May13.204435.3138@cbnewsc.att.com>
Distribution: na
Organization: Private System -- Orlando, FL
Lines: 19

In article <1991May13.204435.3138@cbnewsc.att.com> dcon@cbnewsc.att.com (david.r.connet) writes:
>The kernel debugger for AT&T (as far as I know) is not available
>for the general public.

It's there on ISC 2.0.2; it doesn't seem to be there on ESIX.

>The debugger gives you basically the same abilities as crash, though
>in a very different syntax (I don't know crash's syntax).

What useful things can be done with the debugger?  If I've got a
program that crashes the system, can the debugger help me find the
problem?

I only played with it briefly, but it looked like the debugger could be
a security hole.  You could bring up a debugger session without being
logged on, and probably poke a 0 into the appropriate place in your
uarea...
-- 
John W. Temples -- john@jwt.UUCP (uunet!jwt!john)