Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!decwrl!sgi!key!perry
From: perry@key.COM (Perry The Cynic)
Newsgroups: comp.sources.games.bugs
Subject: Re: Conquer 4 core dump
Summary: Stupid bug
Message-ID: <905@key.COM>
Date: 30 Jun 89 02:27:56 GMT
References: <3448@uokmax.UUCP> <810@dtscp1.UUCP>
Reply-To: perry@arkon.key.COM (Perry The Cynic)
Organization: Key Computer Laboratories, Fremont
Lines: 16

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?

Check out newworl.c, the declaration of newstring[40]. The [40] is grievously
too small, causing a sprintf to it to overflow and spill dirt onto the stack.
Upon return, this garbles the frame pointer, and things get extremely random
from then on.

Make newstring larger (1000 should do), and THIS bug goes away. Stupid, really;
how could this ever work?
  -- perry
-- 
------------------------------------------------------------------------
Perry The Cynic (Peter Kiehtreiber)		     perry@arkon.key.com
** What good signature isn't taken yet? **	   ...!pacbell!key!perry