Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential Stack Frame Corruption from Lua #14

Closed
awdavies opened this issue Oct 6, 2014 · 2 comments
Closed

Potential Stack Frame Corruption from Lua #14

awdavies opened this issue Oct 6, 2014 · 2 comments
Assignees
Labels
Bug The issue in the run-time.

Comments

@awdavies
Copy link
Contributor

awdavies commented Oct 6, 2014

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.

@awdavies awdavies added the Bug The issue in the run-time. label Oct 6, 2014
@awdavies
Copy link
Contributor Author

awdavies commented Oct 6, 2014

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

@nitrocaster nitrocaster self-assigned this Oct 6, 2014
@nitrocaster
Copy link
Member

7d053dc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug The issue in the run-time.
Projects
None yet
Development

No branches or pull requests

2 participants