-
-
Notifications
You must be signed in to change notification settings - Fork 1
-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
enhance memory mapped devices esil support #161
Comments
any news on that? |
cc @condret
afaik no
… On 9 Nov 2018, at 11:10, gordon-quad ***@***.***> wrote:
any news on that?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <https://github.com/radare/radare2/issues/7157#issuecomment-437312989>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3-lp9EG0PyhZ_GkokTx8YurIr_ZIXqks5utVSvgaJpZM4MqH6r>.
|
Is it still considered as "good first issue"? |
This issue has been moved from radareorg/radare2 to radareorg/ideas as we are trying to clean our backlog and this issue has probably been created a long while ago. This is an effort to help contributors understand what are the actionable items they can work on, prioritize issues better and help users find active/duplicated issues more easily. If this is not an enhancement/improvement/general idea but a bug, feel free to ask for re-transfer to main repo. Thanks for your understanding and contribution with this issue. |
Everytime the esil.mdev callback is executed we get the address of memory that is accessed and if the operation is READ or WRITE. but mdev need another 3rd parameter that specifies the value that is written in this address (which can be byte, word, dword,...).
otherwise we cant emulate hw devices
The text was updated successfully, but these errors were encountered: