home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!Germany.EU.net!unido!mikros!mwtech!mecky!walter
- From: walter@mecky.rent-a-guru.de (Walter Mecky)
- Newsgroups: comp.unix.sysv386
- Subject: Re: How to debug a PANIC??
- Keywords: unix panic interactive debug
- Message-ID: <1118@mecky.rent-a-guru.de>
- Date: 27 Jul 92 01:50:58 GMT
- References: <1992Jul13.184212.23816@wb3ffv.ampr.org> <1992Jul24.171942.13964@generics.ka.sub.org> <1992Jul26.151933.22053@tigger.jvnc.net>
- Reply-To: walter@rent-a-guru.de (Walter Mecky)
- Organization: RENT-A-GURU (tm), Buettelborn; FR Germany
- Lines: 29
-
- In article <1992Jul26.151933.22053@tigger.jvnc.net> mtcusa@tigger.jvnc.net (Multilingual Technogies Corporation) writes:
- < Using crash is good advice. I have found that the floppy dump is a pain
- < however. Here's some other ways to find the offending system call:
- <
- < SCO:
- < After the panic, when the system boots, it stops and asks you
- < if you want to go into maint. mode. Type in the password and
- < go into single user. You can then use crash directly on /dev/swap,
- < or do a 'dd' of /dev/swap to some (real big) file somewhere.
-
- < INTERACTIVE:
- < First you have to get the kernel debugger going.
-
-
- Good avices. I'll appreciate it. Here is another one:
-
- SVR4:
- You can add another option in /sbin/dumpsave do save the dump on
- a disk file. Because there may be file system inconsistencies you
- should shift the call of dumpsave in /sbin/bcheckrc after the
- fsck. I testet it and it works. Saves a lot of time even if you
- have a tape.
-
- If somebody wants I mail him/her my modified scripts.
-
- --
- __o Walter Mecky
- _ \<,_ walter@rent-a-guru.de or ...uunet!unido!mikros!walter
- (_)/ (_) Phone: +49 6152 40813
-