[ACC 135] Possible Stack Management Problem

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies
BBCode is OFF
Smilies are ON
Topic review
   

Expand view Topic review: [ACC 135] Possible Stack Management Problem

by MartinHowe » Wed Apr 12, 2006 3:03 am

At last! Now I can go back and re-modularise my code :)

Thanx, Randy

by randi » Tue Apr 11, 2006 7:46 pm

Fixed. The problem was caused by having one function call another function for its result. The VM miscalculated the address of the first function's local variables after it returned from the second function. To reiterate what Graf said, this is a problem with ZDoom and not with ACC.

by Graf Zahl » Fri Aug 26, 2005 3:05 am

If it is a stack problem it is not in ACC. That is done entirely in ZDoom.

by MartinHowe » Fri Aug 26, 2005 3:01 am

I've had a look at the generated code in one of the problem areas, by using the debug file option of ACC, and it doesn't look like it is doing anything it should not. Of course, it could be somewhere else, but could it be a problem somewhere in ZDoom, rather than in ACC?

[ACC 135] Possible Stack Management Problem

by MartinHowe » Thu Aug 25, 2005 4:18 am

In a WAD that I am making, there is a function that maintains part of the map state; it runs every second or so by delaying and restarting.

If the subfunctions it uses are left as functions, the bug manifests - local variables get trashed, including for-loop control variables (leading to a "runaway script" error). If I manually inline the functions and change the variable names to be unique, the bug does not manifest. The attachment includes a text file with a more detailed description.

Has anybody seen this before?

EDIT: Happens with 2.1 as well as 96.

Top