Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!mailrus!ncar!gatech!emory!dtscp1!joel
From: joel@dtscp1.UUCP (Joel Rives)
Newsgroups: comp.sources.games.bugs
Subject: Re: Conquer 4 core dump
Message-ID: <810@dtscp1.UUCP>
Date: 29 Jun 89 15:26:42 GMT
References: <3448@uokmax.UUCP>
Reply-To: joel@dtscp1.UUCP (Joel Rives)
Organization: Digital Transmission Systems (a subsidiary of DCA), Duluth, GA
Lines: 41

In article <3448@uokmax.UUCP> randy@uokmax.UUCP (Longshot) writes:
>Conquer v4 is core-dumping rather nastily when making a new world (conqrun -m).
>Anyone else gotten this, and fixed it?

Yes, i have seen this problem also. The following is a copy of the stack trace
from dbx:

	verify_ntn(__file__ = 0x61cbe "makeworl.c", __line__ = 128), 
							line 53 in "check.c"
	verifydata(__file__ = 0x61cbe "makeworl.c", __line__ = 128), 
							line 133 in "check.c"
	makeworld(rflag = 0), line 128 in "makeworl.c"
	main(argc = bad data address

Note, the bad address for argc in the last line. It looks as if something
is tromping all over the data address space. The following is the source
line and variable information at the spot in verify_ntn() where 'conqrun'
dies:

Source line where execution halts:

	if( sct[a->xloc][a->yloc].altitude==PEAK )

Value of the variable "a" at time of halt:

	*`check`verify_ntn`a = {
	        unittyp = 3
	        xloc    = '"'
	        yloc    = '&'
	        smove   = '\0'
	        sold    = 187
	        stat    = '^C'
	}

However, although subsequent runs always die at the same line, the values
for the "xloc" and "yloc" fields in the structure pointed to by the variable 
"a" vary from run to run. 

I really don't have time to track this down any further.

						Joel Rives