Modern DEBUG?

[Uwar]

I'm looking for some Debugger which works like MS DOS DEBUG (flags and register states after each instruction, memory dumping, ...), but for 32 bit processors and for Windows 5.
Have you ever heard something about ... ?

[sean]

SourceForge.net: XDEBUG - File and System Debbuger

edit: Nevermind- that's not what I thought it was. Being able to read the mbr with java doesn't sound right to me... Try searching around though - that's probably all any of us can do for you. When it got let out that MS-DEBUG wouldn't be in Win7 there was lots of talk about alternatives. Someone on Slashdat mentioned "Open-Debug" but I can't find it - maybe they were kidding.

[Uwar]

Well, after all thank's sean. I will looking around, but Maybe MS DEBUG is the best .

[sean]

You might even have more luck looking for the individual tools you need - like a hex editor, assembler, etc... I'm sure a decent Assembly debugger should give you the features you mentioned. These are just suggestions, though, in case no one else replied - I don't have much experience with that.

[adeyblue]

The Debugging tools for Windows package comes with ntsd, which is a command line debugger. I think it's also included in XP by default.

r to display registers
p to single-step
u to disassemble
Ctrl-Break to break
g to resume
bp for breakpoint
ba for memory breakpoint
k for current thread stack

The full list is in the left pane

[Elysia]

Why not WinDbg?
It's not command-line per se, but it does work with you giving it commands (like command line) via its GUI, and it's a very good debugger at that, for those who do not want to use a graphical debugger.

[brewbuck]

DEBUG is a 16-bit, real mode/VM86 debugger. None of the suggestions so far are even remotely like it.

If you seriously want to work with 16-bit code and use an awful interface, why not install an old copy of DOS on a junky old Pentium?

[matsp]

I second the WinDbg suggestion.

--
Mats

[Uwar]

Ok, thanks a lot for all. I will try WinDbg.

[brewbuck]

I don't think WinDbg can debug a COM file, nor can it call 16-bit real mode interrupts. I don't see how it's a replacement for DEBUG.

[matsp]

I don't think WinDbg can debug a COM file, nor can it call 16-bit real mode interrupts. I don't see how it's a replacement for DEBUG.

Correct, it doesn't support 16-bit mode.

But the original post asked for:

... but for 32 bit processors and for Windows 5.

WinDBG certainly DOES debug 32-bit code.

If, on the other hand, the original poster wanted to debug 16-bit to 32-bit transitions, there is probably a need for hardware assisted debugging, since it's (nearly) impossible for a software solution to single/step or handle breakpoints when transitioning from 16 to 32 or 32 to 16 [or 32 to 64], as the transition changes so many things, including how/where the interrupt vector table is located (which in turn is involved in single-steps and breakpoints).

In a modern AMD processor, it would probably be possible to write a virtual machine monitor (aka hypervisor) that handles the debugging of a virtual machine 16 to 32 and 32 to 64 bit code. However, Intel (at least about 1.5 years ago) did not support 16-bit VM's... And of course, it's still not possible to debug the VM code in a traditional debugger, so you'd better start with something that works. And you couldn't run this in a virtual machine, of course!

--
Mats