Open jduck opened 8 years ago
I suspect much of this can probably already be done. If not through some existing command, then probably through some magic incantation of r2 syntax. If so, a blog or adding this to the migration cheatsheet would go a long long way.
See pxr, pxq and pxQ and related. This was already done a year ago and supports even json output
On 16 May 2016, at 19:27, Joshua J. Drake notifications@github.com wrote:
It should be possible to look at the stack, or other memory area, similar to the way "drr" works. Telescoping is awesome for quick deeper inspection of memory contents.
Bonus points for implementing even more of the things that windbg supports with dereferencing memory. See here: https://msdn.microsoft.com/en-us/library/windows/hardware/ff540451(v=vs.85).aspx
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub
@jduck can we close this one? See also 'tp' - cast some complex type and print the memory contents using this type.
Take a look at what "dp*" things provide in windbg and give concrete examples of how to do the exact same thing in R2. I suspect a gap analysis such as this will show some differences and/or missing features in r2.
@jduck hm, almost every print command could be implemented on top of 'pf'. This is how rabin2 -nn file.exe
is done. If you miss something specific - please make a task list in this bug.
@sivaramaaa you may want to look at this too, just please check http://windbg.info/doc/1-common-cmds.html From what I see the missing thing is 1) better documentation 2) display linked list
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.
Telescoping is awesome for quick deeper inspection of memory contents.
It should be possible to look at the stack, or other memory area, similar to the way "drr" works.Use "pxr @ SP" to see what already exists.Implementing even more of the things that windbg supports with dereferencing memory would be awesome. See here: https://msdn.microsoft.com/en-us/library/windows/hardware/ff540451(v=vs.85).aspx