Open Maijin opened 7 years ago
Related https://github.com/radare/radare2/issues/5934#issuecomment-252429409
On 12 Oct 2016, at 21:28, Maijin notifications@github.com wrote:
From Reverseengineering stackexchange:
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
this is not easy because there are over 9000 flags that can match an offset + delta, so it will be probably be flawed unless the user or the analysis adds a typehint to that instruction (which is not implemented yet)
Hi all. Is there any new for this enhancement?
this is not easy because there are over 9000 flags that can match an offset + delta,
@radare , what about forcing display of user setted flags (for now) ?
For example?
On 30 Jul 2019, at 05:22, mikhi-nde notifications@github.com wrote:
Hi all. Is there any new for this enhancement?
this is not easy because there are over 9000 flags that can match an offset + delta,
@radare , what about forcing display of user setted flags (for now) ?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
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.
From Reverseengineering stackexchange:
http://reverseengineering.stackexchange.com/questions/13696/radare2-how-to-change-operand-from-integer-value-to-flag-offset-in-disassem