Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!decwrl!hal.com!ni From: ni@hal.com (Nathaniel Ingersol) Newsgroups: comp.unix.sysv386 Subject: Re: Kernel core dumps (was Re: out of swap space??) Keywords: forced panic Message-ID: <1991May13.202745.10925@hal.com> Date: 13 May 91 20:27:45 GMT References: <1991May4.232044.3487@NCoast.ORG> <9105122137.aa00923@art-sy.detroit.mi.us> <1991May13.162909.20686@turnkey.tcc.com> Sender: news@hal.com Organization: HaL Computer Systems Lines: 25 In article <1991May13.162909.20686@turnkey.tcc.com> jackv@turnkey.TCC.COM (Jack F. Vogel) writes: :In article <9105122137.aa00923@art-sy.detroit.mi.us> chap@art-sy.detroit.mi.us (j chapman flack) writes: :>[ wants a way to force a system panic...] [...] :kernel. I don't know how far SCO varies from the AT&T standard, but if :you run 'kconfig' (or whatever SCO calls the kernel configurer program) :there should be an option to add facilities to the kernel, when you enter :that submenu one of the facilites you can add is the debugger. Then rebuild :a kernel and presto you have the debugger, you can drop into it at any :particular point by hitting d, then enter the command: :sysdump. If SCO doesn't include this facility you should scream loudly :-}. : Start screaming. SCO will provide a kernel debugger to developers and so on who have an "Engineering Support" contract or something like that, but otherwise a kernel debugger is not part of the standard release. :NO. You could use adb on the running system but then 3.2 doesn't have :adb, oh well... Then again, you can use /etc/_fst, which is a copy of adb that's used for patching kernels...