Disassembly is simply this: a program reads through the binary (the machine code), replacing the op-codes with their equivalent assembly language commands, and outputs the result as a text file.
Infact, the above disassembly compiles back to an object file without error— as sse-add-blk-2.s -o sse-add-blk-2.o —however dont expect this to work for any on larger or executable programs: all the elf metadata, debug info, relocations, data/strings, etc was irrevocably lost.
For best readability though, most debuggers will offer a view that interleaves the disassembly with the original source, so you can compare your code with the compiler's output line by line.
disassembly - How to disassemble a memory range with GDB ... - Stack ...
The quality of the disassembly depends on how much effort you put into it. E.g., if you do not even supply the information that it is an elf file, the disassembly consist of single bytes, and the reassembly is trivial. In the examples I use a script that extracts labels, and makes for a truely usable reverse engineered program that is modifiable.
2 When I'm debugging in uVision 5 the Disassembly window shows the interleaved source code and assembly instructions and the index of the current executed instruction. I need this window exported in a file in order to parse it with an exported code coverage report.
How to change the disassembly syntax to intel using gdb? Asked 7 years, 1 month ago Modified 2 years, 6 months ago Viewed 26k times
1 If you are talking about debugging to see the assembly code, the easiest way is Debug->Windows->Disassembly (or Alt-8). This will let you step into a called function and stay in Disassembly.