Date: Wed, 23 Sep 1998 13:49:02 -0700 From: Mike Smith <mike@smith.net.au> To: Johann Visagie <wjv@cityip.co.za> Cc: =?iso-8859-1?Q?Dag-Erling_C=2E_Sm=F8rgrav_?= <dag-erli@ifi.uio.no>, Mike Smith <mike@smith.net.au>, chat@FreeBSD.ORG Subject: Re: Debugging, Linux style Message-ID: <199809232049.NAA03869@dingo.cdrom.com> In-Reply-To: Your message of "Wed, 23 Sep 1998 15:10:53 %2B0200." <19980923151053.B9294@cityip.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, 22 Sep 1998 at 23:05 SAT, Dag-Erling C. Smørgrav wrote: > > > > The term "shotgun debugging" comes to mind. > > Out of curiosity, what would be a valid procedure to follow in order to debug > that user's problem? A 1:1 dialog with the user, involving the replacement of various hardware components, extraction of more debugging information, etc. > (Also: I've heard that certain versions of the Virge cause lockups when used > with certain PII chipsets, but that might be hearsay.) I have personally witnessed fatal interactions between the ViRGE VX and DX chips and the 440FX PCI implementation. I have a 4M DX going cheap if someone is game. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809232049.NAA03869>