Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!turnkey!jackv From: jackv@turnkey.tcc.com (Jack F. Vogel) Newsgroups: comp.unix.sysv386 Subject: Re: Kernel core dumps (was Re: out of swap space??) Keywords: forced panic Message-ID: <1991May13.162909.20686@turnkey.tcc.com> Date: 13 May 91 16:29:09 GMT References: <450@bartal.BARTAL.COM> <9105031411.aa04050@art-sy.detroit.mi.us> <1991May04.132158.17121@turnkey.tcc.com> <1991May4.232044.3487@NCoast.ORG> <9105122137.aa00923@art-sy.detroit.mi.us> Reply-To: jackv@turnkey.TCC.COM (Jack F. Vogel) Organization: Turnkey Computer Consultants, Westchester, CA Lines: 31 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...] >One person suggested using the kernel debugger; several suggested using >`crash' to look at the running system. I don't have a development system >and I haven't found anything lying around that looks like a kernel debugger, >so I doubt that linking that in is an option for me. You don't need the development system, and the "debugger" is not some binary that you would find "lying around". It should be an option in linking your 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 :-}. >Is there some undocumented way to >modify things with `crash'? NO. You could use adb on the running system but then 3.2 doesn't have adb, oh well... Disclaimer: I'm paid to fix bugs, not to speak for the company! -- Jack F. Vogel jackv@locus.com AIX370 Technical Support - or - Locus Computing Corp. jackv@turnkey.TCC.COM