search

radareorg / ideas

4 stars 1 forks source link

Deeper analysis of TMS320 C55x #5

Open XVilka opened 10 years ago

XVilka commented 10 years ago

@milabs like this for example https://github.com/radare/radare2/blob/master/libr/anal/p/anal_x86_udis.c#L295

XVilka commented 10 years ago

Or even better example https://github.com/radare/radare2/blob/master/libr/anal/p/anal_gb.c

milabs commented 10 years ago

@XVilka Что это и зачем?

XVilka commented 10 years ago

@milabs I mean not just opcode type, but some additional information for stack, movs etc.

radare commented 10 years ago

what about esil? and deeper RAnalOp info?

condret commented 10 years ago

@XVilka could you provide something like an opcode-table, similar to this http://www.villehelin.com/mnemonics_gb_o.txt A register-table would be usefull, too. And probably a paper about hardware-bugs, if there are any.

Maybe I could spend some time on this.

XVilka commented 9 years ago

@condret I have datasheets, if you want.

ret2libc commented 4 years ago

This issue is going to be 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.