Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!samsung!sdd.hp.com!think.com!cayman!brad From: brad@Cayman.COM (Brad Parker) Newsgroups: comp.unix.bsd Subject: Re: kdb kgdb and dump Message-ID: <BRAD.92Jun23130722@haiti.Cayman.COM> Date: 23 Jun 92 17:07:22 GMT References: <cproto.709305090@marsh> Sender: news@cayman.COM Organization: Cayman Systems Inc., Cambridge, MA Lines: 21 Nntp-Posting-Host: haiti In-reply-to: cproto@marsh.cs.curtin.edu.au's message of 23 Jun 92 13:11:30 GMT In article <cproto.709305090@marsh> cproto@marsh.cs.curtin.edu.au (Computer Protocol) writes: Has anybody got some sort of a kernel debugger working for 386bsd ??? no; gdb -k -w works, but you can't (or *I* can't) change any kernel memory space because the process is not "running". I'm desperate to get dump working. The previously suggested fix of reducing the number of slaves to 1 doesn't work. I still have got 3 hanging dump processes. One of which is in a noninterruptable disk i/o wait. For the moment I'm using tar but I would much prefer dump. Any suggestions please ?!? It worked for me! (i.e. changing SLAVES from 3 to 1); make sure you have the ast fix. -brad -- A metaphor is like a simile. Brad Parker Cayman Systems, Inc., Cambridge, Ma. brad@cayman.com