WHICH DEBUGGER AM I USING?

[NUMBSKULL2]

I downloaded MASM32 SDK Version 10
From the command line in what I think is a "command shell" window, I typed in
Debug filename.exe
The .exe file is loaded into memory and I get a new prompt character which I think is the hyphen "-". I have figured out  several of the simplest commands,yet have not found the commands I was hoping for.Can anyone tell me which debugger this is and where can I find a listing of all of the commands that this debugger supports? :bg

[donkey]

debug.exe is the MSDOS debug command, not much of a debugger (not really one at all). It is found in the System32 folder of most Windows installations. Type ? at the prompt (-) for a command/keyword listing though the only really useful command for Debug is "quit".You may also want to run EDLIN as your IDE ;)

[ChrisLeslie]

You may also want to run EDLIN as your IDE

Don't laugh, but as of a mere few years ago the was a chap at Geoscience Australia who still insisted on using EDLIN as his prefered text editor  :eek.

[MichaelW]

Debug was good in its day and still useful for debugging 16-bit DOS applications and for experimenting with the 8086/8088 instruction set. IMO these programming courses that are focused on coding 16-bit DOS applications with MASM should be pushing Debug both as the an entry point and as the debugger. For Windows programming I agree that it's pretty much useless, as was EDLIN, even in its day.

[dedndave]

    I never liked EDLIN - lol. I used a program called PCWrite back in the old days. In fact, I used debug and PCWrite together to disassemble the better part of many of the DOS versions.
   As I am new to 32-bit code, I have looked at several debuggers. The "debug" function is far more complex for 32-bit use. I am sure that, like everything else, my preference will lean toward the first one to which I grow accustomed.
   Here are a couple debuggers that I am trying out.....

Microsoft:
http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx

OllyDbg:
http://www.ollydbg.de/

   For 32-bit work, there seems to be a need for much more than a debugger......

HxD (hex file editor):
http://mh-nexus.de/en/hxd/

DumpPE (PE file format viewer):
http://www.tbcnet.com/~clive/vcomwinp.html

PEView (PE/COFF viewer):
http://www.magma.ca/~wjr/

   As I learn more, I know I will find the need for several other types of tools for 32-bit work. If the past is any indicator, by the time I am a 32-bit "expert", the rest of the world will be writting 256-bit code - lol.

- Dave

[donkey]

Although I swear by Olly and PEView, don't forget the smidgeonsoft tools, they are excellent and provide functionality that many others don't...

http://www.smidgeonsoft.prohosting.com/software.html

[GreenTea]

I downloaded MASM32 SDK Version 10
From the command line in what I think is a "command shell" window, I typed in
Debug filename.exe
The .exe file is loaded into memory and I get a new prompt character which I think is the hyphen "-". I have figured out  several of the simplest commands,yet have not found the commands I was hoping for.Can anyone tell me which debugger this is and where can I find a listing of all of the commands that this debugger supports?

If all you intend to do is write and debug 32 bit apps, use the suggestions from the responses you get.

GRDB is a 32 bit debugger that is free.

Since there are many assemblers that make programs, using a command line debugger has some advantages.

Ex. Using the dump command allows you to see embedded text that other debuggers won't show
     because they have to make some assumptions about what program made the .exe or .com

Another good tool is IDAFW which can give you a .asm file that can usually be assembled fine
by Masm.

You may want to consider keeping some 16 bit apps around to fine tune to your needs.
They have the advantage of working on any MS OS right up to XP.

Good luck.