C Programming, Disassembly, Debugging, Linux, GDB
A brief introduction to GDB and Assembly Language on Intel processors using the venerable C language and GCC compiler toolchain. This is probably more fun than it is informative (and not even all that fun), but maybe it will give somebody ideas… Documentation: man wprintf man gdb man objdump man hexdump Use pinfo -m instead of man for a nice, colorful interface that can be navigated by clicking or using the arrow keys. Making simple programs and analysing them with a debugger such as GDB …
Related posts:
Loading ...
It’s not an IDE. It’s the scite text editor. The LINUX Operating System itself is my Integrated Development Environment (IDE)! I used the Compiz window manager to glue scite and terminal windows together and flip them around in 3D. I also added a bunch of lua script add-ons from the scite lua script page. All free.
please till me what is the name of this IDE
ndisasm comes bundled with the Netwide Assembler (nasm) package.
I used Turbo Debugger a lot in MS-DOS days, gdb is a simple version, command version, and I heard of ELF on Linux, and I can see what you were doing by anti-debugging with hexdump, but what on earth is ndisasm? I didnt get that.
I am preparing to crack some anti debugger code.
Didn’t get why you used hexdump. What was that doing?
There are much better videos on gdb, conditional breakpoints and such. I only had time to touch on a few tools. Also forgot to mention that the terminal should support wide character streams (most do, although gdb doesn’t appear to yet…)
Nicely done, thanks..
[...] Link to the original site VN:F [1.4.5_712]please wait…Rating: 0.0/10 (0 votes cast) [...]