chinn@butler.UUCP (David Chinn) (05/31/86)
A little while ago, while being a guest on a neighboring
system, I ran dbx on a program and crashed the entire system!
I checked with their SA and he said that he knew it was
a problem and was trying to get around to fixing it.
Recently, however, their SA moved out of state, and I find
that I will have to be using their system for some serious
work.
So the question is, is this a known problem with DBX and is there
a fix? They are running Berkley's 4.2 on a 750 with a single
RA81. They also have source licence.
Thanks Much
... uw-beaver david m chinn
!tikal!dataio box 639
!butler!chinn redmond, wash 98073chris@umcp-cs.UUCP (Chris Torek) (06/02/86)
Find calls to munhash() and mfind() that cast the second argument, c->c_blkno, to `(daddr_t)(u_long)'. There are two, one in /sys/sys/vm_mem.c and one in /sys/vax/vm_machdep.c. Remove the (daddr_t). The new code is technically wrong, but makes the compiler do the right thing. `Fixed in 4.3!' -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1516) UUCP: seismo!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@mimsy.umd.edu