Timeline for Use GCC and objdump to disassemble any hex to assembly code
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 6, 2020 at 10:12 | answer | added | Willem Hengeveld | timeline score: 2 | |
| Mar 1, 2020 at 19:53 | answer | added | blabb | timeline score: 0 | |
| Feb 29, 2020 at 6:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 1, 2019 at 5:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 2, 2019 at 19:28 | comment | added | tecMav | Thank you all. Was hoping to do with just gcc and objdump. One thought was can I have binary data in the c or s file, compile them, and then be do a objdump to get the disassembly. Any thoughts in that line? | |
| Oct 1, 2019 at 18:15 | comment | added | blabb | reverseengineering.stackexchange.com/questions/17946/… | |
| Oct 1, 2019 at 18:07 | comment | added | smitelli |
Would it need to do much more than echo -ne "\x55" | ndisasm - does?
|
|
| Oct 1, 2019 at 18:07 | comment | added | Paweł Łukasik |
the fastest for me: rasm2 -d -a x86 0x55
|
|
| Oct 1, 2019 at 18:06 | answer | added | julian♦ | timeline score: 3 | |
| Oct 1, 2019 at 17:14 | history | edited | tecMav | CC BY-SA 4.0 |
deleted 3 characters in body
|
| Oct 1, 2019 at 16:53 | comment | added | bart1e | The fastest way I know is to use this site although it’s not command line tool. " It uses GCC and objdump behind the scenes." though. | |
| Oct 1, 2019 at 16:45 | review | First posts | |||
| Oct 2, 2019 at 8:53 | |||||
| Oct 1, 2019 at 16:40 | history | asked | tecMav | CC BY-SA 4.0 |