-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
RIP size on x86-64 #80
Comments
I will fix it in a following PR ( with another way ) , wait for me😅 |
random thought: it might be nice to statically type-encode the size of the registers when when they're passed to the read/write_registers. One way could be to move the I'm thinking that might save some slice length checks when implementing these functions. But not sure if even possible just a thought :) |
@gz I assume you meant If so, then you might find this discussion from the initial implementation PR interesting: #22 (comment) Though now that I'm re-reading this idea a year later, I realize that there might be some easier approaches to pull off something similar... I certainly wouldn't be opposed to having stricter type-safety in these APIs, so I'm open to any ideas! |
Yes I meant the single register writes with the dynamic |
Sent pull request, yes would be nice to have this fixed, thanks! |
rip size is currently 4 bytes, but maybe it should be 8?
https://github.com/bminor/binutils-gdb/blob/master/gdb/features/i386/64bit-core.xml lists it as:
The text was updated successfully, but these errors were encountered: