You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Examining the stack trace of an error caused by loading a game in the current build, some addresses appear to become corrupted after some Lua-related functions are called.
ex:
the original stack content: 0018B418 048F13C9 ЙSЏ; /RETURN from xrGame.CGameObject::shedule_Update to xrGame.048F13C9
gets modified to: 0018B418 008F13C9 ЙSЏ; /RETURN from xrGame.CGameObject::shedule_Update to xrGame.048F13C9
after the call_member function is called. This appears to be some sort of stack corruption, which will have nasty (and undetermined) effects in code execution. Notice the address change from 048F13C9 to 008F13C9.
This is somewhat related to the ongoing effort to fix #11.
The text was updated successfully, but these errors were encountered:
Further investigation by @nitrocaster reveals the issue may have to do with XRay's console, which appears to cause a buffer overflow, overwriting the stack frame :c
Examining the stack trace of an error caused by loading a game in the current build, some addresses appear to become corrupted after some Lua-related functions are called.
ex:
the original stack content:
0018B418 048F13C9 ЙSЏ; /RETURN from xrGame.CGameObject::shedule_Update to xrGame.048F13C9
gets modified to:
0018B418 008F13C9 ЙSЏ; /RETURN from xrGame.CGameObject::shedule_Update to xrGame.048F13C9
after the
call_member
function is called. This appears to be some sort of stack corruption, which will have nasty (and undetermined) effects in code execution. Notice the address change from048F13C9
to008F13C9
.This is somewhat related to the ongoing effort to fix #11.
The text was updated successfully, but these errors were encountered: