Surprised I haven't seen this posted here before, nor could I find it searching. Worth a post, none the less: Found another rather decent amd64 debugger for Windows.

http://duxcore.com/index.php/prod/visual-duxdebugger/overview

Interface has some nice features: I like how the machine code bytes are partitioned logically based on contribution to instruction. Also watch and register windows reflect changes in alternate color. Display seems very flexible and featureful (uses MFC dock manager).

Display of import calls don't show symbolically until it's the next instruction. Going to play with it some more...

Disassembly is done by:
http://code.google.com/p/distorm/

seems to be excellent debugger
the company producing it is in the country where LocoDelAssembly lives

[ Post removed by author. ]

dont cry for me

[ Post removed by author. ]

[ Post removed by author. ]

Haven't heard about it nor use it myself. Can anyone provide some more details about working with it? I had used distorm in the past but now part of it is a commercial product and it would not fit some of research I'm doing.

Well, my biggest complaint with the debugger is the lack of UI state saving - basically, makes it unusable in the long-term. FDGB saves window positions so I have even have different copies of the program to load different configurations of windows.

For example, I like to have a good view of the stack and a couple memory locations. If I need to spend five minutes moving things around before I start reading the instruction stream - es no bueno.

distorm3 seems okay, but pintools might be more useful. The license on pintools is even more restrictive, though. If I did a commercial project the intelligent user would need to drop-in the restricted DLLs. Freeing me of the headache, and putting the legal burden on them.

This debugger sucks. I can't see an active process which other debuggers can see and shows up in Task Manager.

Verdict: Piece of shit. Wasted time on GUI features instead of functionality.

Can't even debug some programs. WTF? Waste of space on my PC

[ Post removed by author. ]

typedef, I completely disagree. This debugger is a work in progress, and much work has been put into processing the output from diStorm, and maintaining context state. The UI is MFC - which he doesn't really use the 4mb of images in the resource section of the program! Dynamic compilation would have been a good idea - to use the mfc.dll.

Of course, it's easy to criticize - these are small things - nitpicking.

Aah... Fuck ! I was trying to debug a 32-bit app then.

Oh well, first impressions.

I didn't even read the damn title. LOL

Ok, so at this point I'm not interested since I need a debugger that can handle both 32/64 bit apps under Windows. There is already a good set of debuggers which can handle only one type of apps. Anyway it is good to know about new debugger that already has some potential.

^^^quote fail

Done

I thought the whole post was a quote until you fixed it.

Careful when quoting