Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 (MC830713); site hwcs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!cbosgd!ihnp4!houxm!houxz!vax135!ukc!edcaad!hwcs!andrew
From: andrew@hwcs.UUCP (Andrew Stewart)
Newsgroups: net.bugs.4bsd,net.unix-wizards
Subject: dbx causes 4.2 to panic.....
Message-ID: <131@hwcs.UUCP>
Date: Fri, 27-Jul-84 06:43:19 EDT
Article-I.D.: hwcs.131
Posted: Fri Jul 27 06:43:19 1984
Date-Received: Wed, 18-Jul-84 02:16:47 EDT
Distribution: net.bugs.4bsd,net.unix-wizards
Organization: Computer Sci., Heriot-Watt U., Scotland
Lines: 20

<munch, munch>

Has anyone seen this happen under 4.2BSD on a VAX (or anything else)?.....
SU to root and run dbx on CProlog with a core dump.
Type a few harmless commands (status, help, print) - the print should display
the values of things like argc, argv, argp at core-dump time.
Now type "run".. the system produces the console message
"panic: munhash"
which is an error caused by trying to pick something off the clist hash list
which isn't there. It is also, according to a comment in the kernel, a
"can't happen" error. Sigh....

If anyone has seen this and fixed it, or has any pointers to what is going on,
could you please mail me? Or post a reply to this group?

Cheers....
----------------
"Not a bug, a feature! It's documented, dash it!"
	Andrew Stewart.
	...!vax135!ukc!edcaad!hwcs!andrew	(uucp)