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.

Sign up for GitHub

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

Jump to bottom

Design Documentation #1

Open
leegao opened this issue Jul 22, 2020 · 2 comments
Open

Design Documentation #1

leegao opened this issue Jul 22, 2020 · 2 comments

Comments

@leegao
Copy link

leegao commented Jul 22, 2020

This is a really really clever design to integrate LuaJIT. If I'm reading this correctly, essentially you're finding the function addresses for the lua API functions (even if these aren't exported) and you're hot patching these with trampoline jumps to redirect them into your own runtime.

I think it may be helpful for interested readers and potential contributors to elaborate on the larger design/architecture of how you accomplish this, and the types of tradeoffs you have encountered.

For example, how do you find the offsets of these API functions?
@MikuAuahDark
Copy link
Owner

how do you find the offsets of these API functions?

Ghidra and Lua 5.1.4 source code.

MikuAuahDark added a commit that referenced this issue Apr 21, 2021
@MikuAuahDark
Add Design/How it Works tab
16884d6 
Issue #1
@MikuAuahDark
Copy link
Owner

Is the information in the updated README sufficient?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@leegao @MikuAuahDark