Dump memory range with hopper disassembler

#Dump memory range with hopper disassembler software
#Dump memory range with hopper disassembler code

Tough often I really missed this functionality.ДЈ.1 Limitations of objdump based disassemblersДЄs I have often been asked - so what are the limitations of objdump? First to say, objdump expects to get a nicely compiled executable by gcc. This of course only makes limited sense as it is not a debugger. also you will be able to directly work with the programs data and for example pass it to several customizable en-/decryption routines.

#Dump memory range with hopper disassembler code

The code can be scanned for custom sequences, known antidebugging techniques, known encryption algorithms. The more exotic features of lida should be on the analysis side. Therefore lida will have an integrated patcher, resolves symbolic names, provides the ability to comment the code, serves efficient browsing methods. Everybody who has already worked on some deadlisting will immediate feel a need to work interactive with the code - and be able to change it. The several limitations of objdump (see 3.1) are broken by using libdisasm (thx to HCUNIX!), and by tracing the execution flow of the program.ДЇurther, by having the control over the disassembly - more features can be included.

Many disassemblers out there use the output of objdump - lida tries a more serious approach. lida should be a good 'entry point' for examining the 'new targets'.ДЄ typical use is to run it while debugging your program and comment the deadlisting / name functions with the information gathered. Lida addresses people who like to work on deadlistings, and should be especially useful for people with previous experience in windows reverse engineering. Therefore it is designed to (and should) fit several needs of some typical reverse-engineering sessions.

#Dump memory range with hopper disassembler software

The project lida was initiated because of the lack of handy reverse engineering software for linux.

openssl support (customizeable 'init values', apply to programs datablocks).

scan for known anti-debugging, anti-disassembling techniques.

work with symbolic names: interactive naming of functions, labels, commenting of code.

ELF, RAW file disassembly (generating stringtable, symboltable, crossreferences.

It allows interactive control over the generated deadlisting via commands and builtin tools. It uses the bastards libdisasm for single opcode decoding (see ). Lida is basically a disassembler and code analysis tool. Some words about the disassembling engine Limitations of objdump based disassemblers Linux Interactive DisAssembler - Project Homepage Lida - Linux Interactive DisAssembler last updated: 05.12.04 21:03