Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!chinacat!sequoia!rpp386!jfh From: jfh@rpp386.cactus.org (John F Haugh II) Newsgroups: comp.unix.wizards Subject: Re: Making sense of a system coredump Message-ID: <19384@rpp386.cactus.org> Date: 14 Jun 91 12:48:33 GMT References: <1991Jun13.220751.26994@convex.com> Reply-To: jfh@rpp386.cactus.org (John F Haugh II) Distribution: comp.unix.wizards Organization: Lone Star Cat Grill and Sushi Bar, The Republic of Texas Lines: 13 X-Clever-Slogan: Please send money. I need another NRA Life Membership. In article <1991Jun13.220751.26994@convex.com> bout@convex.com (David Boutilier) writes: >I'm afraid you're pretty much stuck with using adb. To the best of my >knowledge, no other debugger will work effectively with the kernel. Not that his system actually has the "crash" command, but that is my preferred tool. You typically can find out what module was being executed that caused the panic as well as the location (if you are handy with ADB). -- John F. Haugh II | Distribution to | UUCP: ...!cs.utexas.edu!rpp386!jfh Ma Bell: (512) 255-8251 | GEnie PROHIBITED :-) | Domain: jfh@rpp386.cactus.org "UNIX signals are not interrupts. Worse, SIGCHLD/SIGCLD is not even a UNIX signal, it's an abomination." -- Doug Gwyn