Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!adb
From: adb@bu-cs.BU.EDU (Adam Bryant)
Newsgroups: comp.sources.games.bugs
Subject: Re: Conquer 4 core dump
Message-ID: <33980@bu-cs.BU.EDU>
Date: 28 Jun 89 23:49:59 GMT
References: <3448@uokmax.UUCP>
Reply-To: adb@bu-it.bu.edu (Adam Bryant)
Followup-To: comp.sources.games.bugs
Organization: Boston University Obscure Personality Society
Lines: 45

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?
>
> Randy

I think the makeworld actually completes properly before the dump.  So
the data file should be valid, and continuing on from there should work.
If this is not the case, please let me know.

I believe the dump is being caused by the isonfile variable being
changed somewhere within the makeworld() function.  I have not traced
the cause of this yet [probably some memory overwrite within the
makeworld() routine].

The patch below should avoid the dump altogether.

adam

ps.  This is not an official patch, just a little one to avoid
 the dump for now...

*** oadmin.c	Wed Jun 28 19:32:04 1989
--- admin.c	Sun Jun 18 18:11:41 1989
***************
*** 122,130 ****
  		exit(FAIL);
  	}
  	if((mflag)||(rflag)) {
- 		makeworld(rflag);
  		sprintf(string,"%sup",isonfile);
  		unlink(string);
  		exit(SUCCESS);
  	}
  
--- 122,130 ----
  		exit(FAIL);
  	}
  	if((mflag)||(rflag)) {
  		sprintf(string,"%sup",isonfile);
  		unlink(string);
+ 		makeworld(rflag);
  		exit(SUCCESS);
  	}