Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ukma!rutgers!att!occrsh!rjd
From: rjd@occrsh.ATT.COM (Randy_Davis)
Newsgroups: comp.sources.games.bugs
Subject: Re: Nethack 3.0 compile hassle
Summary: Fixed it.
Message-ID: <826@occrsh.ATT.COM>
Date: 2 Aug 89 18:32:23 GMT
References: <217@labii.UUCP> <824@occrsh.ATT.COM>
Reply-To: rjd@occrsh.UUCP (Randy_Davis)
Distribution: na
Organization: AT&T Network & Data Systems, OKC
Lines: 22

In article <824@occrsh.ATT.COM> rjd@occrsh.UUCP (Randy_Davis) writes:
|  Of course, now it is "Memory faulting" after picking the character class
|whether you or it does it, so I am now putting some tracing prints in the
|code so I can find the offending statements.
|
|  Can anyone who has delt with the Memory Fault after picking the character
|class save me some time on this bug?  (Email preferable for speed sake, feel
|free to also post).

  Hold the presses....  I found the fix to the problem I pose above.  It
turns out (20 compiles later and putting in LOTS of tracing printf's) that
I traced it down to the mkroom structure that uses the schar typedef.  I
*HAD* (honest!!) changed the typedef of schar to short int according to the
authors' instructions (running on a 3B2), yet that editing session got hung
up on when I was at home and got a phone call (ain't call-waiting a pain
sometimes?).  I had forgotten it and missed re-doing it...  So.. NOW nethack
is working until I find a bug in the actual operation of it.

Thanks anyway,

Randy Davis			UUCP: ...(att!)ocrjd!randy, randy@ocrjd.att.com
				      ...(att!)occrsh!rjd,  rjd@occrsh.att.com