Talk:X86 Disassembly/Analysis Tools

We can bump this page up to 50% completed if we can list a few Linux debuggers. beyond that, we should probably include some screenshots, and some tips on effective debugging (perhaps even make a distinction between live analysis and dead listing). --Whiteknight 03:54, 20 September 2005 (UTC)

I think some of the Linux-debuggers here are not "debuggers" per se at all. Some of them should probably be moved to the "other tools" section, but i dont know this for a fact. --129.32.61.137 13:47, 20 September 2005 (UTC)


 * Can you define what a "debugger" is? I can use those tools for debugging; therefore they are debuggers. :-) The page isn't called "traditional debuggers" or "interactive debuggers" or "GUI debuggers". Weird scriptable tools can be very powerful. AlbertCahalan 14:16, 20 September 2005 (UTC)
 * Good point, but some of the tools, specifically readelf or objdump fit better into the section on "Other tools", as a counterpoint to the windows dumpbin utility already listed there. I've been defining debugger as a program that allows single-stepping, breakpoints, and analysis. Tools not specifically used in this manner have been moved to the "Other tools" section. It is important to focus on few issues per chapter, to prevent confusing the reader. If the book says that every reader should have "at least one debugger" when reading this book, it would probably be counterproductive if the reader only downloads Lizard or ReadELF, because those dont do the job that "debuggers" do in this book.--Whiteknight
 * I think Lizard does single-stepping... in both directions! AlbertCahalan 00:01, 22 September 2005 (UTC)
 * Well if it does allow single-stepping, then perhaps we can include it here as well, although i dont think it has a particularly bad home in the "Other Tools" page. --Whiteknight 19:36, 7 October 2005 (UTC)