Path: chuka.playstation.co.uk!chuka.playstation.co.uk!scea!greg_labrec@interactive.sony.com From: Spellweaver Newsgroups: scea.yaroze.problems.pc,scea.yaroze.programming.codewarrior Subject: Re: Yet Another CodeWarrior Problem Date: Sat, 20 Sep 1997 14:01:22 -0500 Organization: The Implementor Lines: 21 Message-ID: <34241D82.4BB5@ix.netcom.com> References: <34236F6C.16A9@ix.netcom.com> <01bcc597$80ca33c0$81bf43ce@wkwerner> Reply-To: spelwevr@ix.netcom.com NNTP-Posting-Host: norn.tiphares.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.02 (WinNT; I) Xref: chuka.playstation.co.uk scea.yaroze.problems.pc:143 scea.yaroze.programming.codewarrior:199 Quoth thee: [ ... ] > I didn't get a chance to check out your code to see what you're > doing, but it is my experience that when the order of definition > of automatic variables changes the behavior of a program, it is > usually due to a memory overwrite. [ ... ] > I doubt that the CW compiler is failing at something as basic as > setting up automatic variables on the stack. If this were the > case, CW would be hard pressed to make even the most basic hello > world program work. [ ... ] I, too, thought that it might be an overrun error, but as I mentioned, I have had this occur before when the variables involved were such simple types as ints, when no pointer or structure access was involved. It doesn't happen frequently; only under certain conditions, which I haven't nailed down yet. However, it seems to occur in such widely varied programs, with essentially no common code, that I doubt that could be a wild pointer or something of the sort in every instance (unless it is in the rtl or Yaroze libs themselves).