Open crowell opened 8 years ago
This is already done, but not for dbg.slow
On 26 Apr 2016, at 07:50, Jeffrey Crowell notifications@github.com wrote:
colorize registers based on values (pointing to code, etc.) like the stack is done currently, and is done in peda.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub
@sivaramaaa see this too
Yup i could give it a try , i too felt the need for it , also dbg.slow in genereal itself needs some improvement , for example the register output itself take all the space and u could barely see the instructions !!!
One option would be to not show the registers that are 0 or only the ones used in context. So we may do 2 passes here. One to get all the regs involved in the pd and then another dr to show only those
On 18 Feb 2018, at 07:20, sivaramaaa notifications@github.com wrote:
Yup i could give it a try , i too felt the need for it , also dbg.slow in genereal itself needs some improvement , for example the register output itself take all the space and u could barely see the instructions !!!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Yep that's sounds to be a much better option , i could try to do this !!!
check the ‘aea’ command
On 18 Feb 2018, at 14:00, sivaramaaa notifications@github.com wrote:
Yep that's sounds to be a much better option , i could try to do this !!!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/radare/radare2/issues/4714#issuecomment-366514507, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3-lmxsbe0OypRv-5AAxqlx1By4BCcTks5tWB8JgaJpZM4IPnau.
maybe its easier to modify aea to show the regs like dr= does, with aer= or so than doing it the other way around.
On 19 Feb 2018, at 14:38, Pancake Nopcode pancake@nopcode.org wrote:
check the ‘aea’ command
On 18 Feb 2018, at 14:00, sivaramaaa <notifications@github.com mailto:notifications@github.com> wrote:
Yep that's sounds to be a much better option , i could try to do this !!!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/radare/radare2/issues/4714#issuecomment-366514507, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3-lmxsbe0OypRv-5AAxqlx1By4BCcTks5tWB8JgaJpZM4IPnau.
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.
I think this is VERY useful, and pretty easy to implement, the only problem is the conflict with the current register colorization based on regdiffing. we can use BOLD attribute for that instead for example
colorize registers based on values (pointing to code, etc.) like the stack is done currently, and is done in peda.