-
Notifications
You must be signed in to change notification settings - Fork 149
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
Auto assembler like in Cheat Engine #232
Comments
It's in the roadmap. Scripting and assembler are already available but they are not integrated into GUI yet. Libpince engine is the scripting support and it actually is the next step in the roadmap so this feature will be most likely implemented within next year. I'll update this issue once it's complete. Here's the roadmap if you are interested Edit: To clarify, you can already inject single-line asm by right clicking on the disassemble window but not trampoline code, that's what I meant when I said "not integrated into GUI yet" |
How would I use the scripting and assembler without GUI? I'm willing to read the documentation in libpince to do it manually in the meantime. |
Open a console in pince root folder and activate the python env, then launch python with root privs like
This will let you use the libs required by pince, they are installed locally. To attach to your process, you can use this code snippet: from libpince import debugcore, utils
pid = utils.search_processes("process name")[0][0]
debugcore.attach(pid)
debugcore.interrupt_inferior() This basically searches for your process and returns the first match, then attaches and stops it. To continue the process, you can use You can use |
speaking of cheat engine any plans to have a way to import cheat engine tables ? |
No, there won't be such a thing as it doesn't make sense. Memory layout between Windows and Linux are different so the table would still need to be modified for it to work. |
I was wondering if there could be (or already is an) auto assembler in PINCE. I'd like to search big-endian floats in RPCS3 using scripts like this:
The text was updated successfully, but these errors were encountered: