Hi,

I urgently need link on debugger which is able to run under windows 2000... If you know anything i ll be very grateful
thanks
Posted on 2002-01-10 06:38:14 by Marty
Hi Marty !

Here's a recent thread discussing about debuggers...

http://www.asmcommunity.net/board/index.php?topic=1904


For a ring3 debugger, I recommend you to use OllyDBG which I think is fairly good (works perfectly on 2000... even better than 9x).
Posted on 2002-01-10 07:13:59 by JCP
I would offer two suggestions, however they may both cost you some money.

The top candidate has to be SoftIce, however i believe NuMega still don't have an installer for Win2K, you are limited to installing the NT4 version, then applying a new symbol file and some patches. Last time i looked, you can get a trial version (30 day limit) if you go to their website, register for Driver Studio, and are prepared to run the gauntlet with their sales people :). I recommend that you do look at purchasing this eventually, it is a great product.

My other option would be to use VC6. You can set up your asm projects in it, then step through the source code in debug mode, that ability can help you emmensly to write a good stable bug-free app. The academic version of VC6 is really cheap, and i believe it has just about all the capabilities of the full version.
Posted on 2002-01-10 14:53:39 by sluggy
My other option would be to use VC6. You can set up your asm projects in it, then step through the source code in debug mode, that ability can help you emmensly to write a good stable bug-free app. The academic version of VC6 is really cheap, and i believe it has just about all the capabilities of the full version.


I have VC6 and I couldn't figure out how to get asm files to work in projects. I couldn't find the project options that allow me to compile asm to obj or enable debugging of an asm obj. :confused: Could you fill me in? Thanks.
Posted on 2002-01-10 17:10:15 by Mecurius
Here you go... i have cut and pasted this from a newsgroup posting, and it works great. Once you have the project set up, you can do all the usual dragging & dropping of files between the folders in the file explorer pane, add new files to it, etc.


Procedure for creating a new MASM project in Visual Studio 6.0:

1. Put your MASM files (e.g., ml.exe) in any directory
you want. In Visual Studio, include that directory in Tools ? Options ?
Directories. When you assemble, Visual Studio will search for the MASM
files there. Also include the directories where you have your include
files. This process only needs to be done once; it remains a ?global?
setting for all MASM projects you subsequently create.

2. Create a new project (as a Win32 application) with
the same name as your ASM file. It should create a blank Win32 workspace by
the same name.

3. Copy your ASM and resource file(s) into the project
directory. Then Click ?Project? at the top of the window, then choose ?Add
to Project? and choose ?Files.? Add in your ASM file and your resource file
(.RC file). The RC file must also have the same name as the ASM file.

4. Select (click on) the name of your ASM file or files,
then either right click or click ?Project? at the top of the window, and
choose ?Settings.? Under the ?Custom Build? tab, insert the following in
the box headed ?Commands.?

ml /c /Cx /coff /Cp /Zi /Zd $(InputPath)

Put in the $(InputPath) by clicking on the ?Files?
button at the bottom and choosing Input Path. Do not put in the name of
your ASM file; Visual Studio will do it for you.

Then insert the following in the box headed
?Outputs.?

$(InputName).obj

Again, put in the $(InputName) by clicking on the
?Files? button at the bottom and choosing Input Name, and append .obj to the
end. Do not put in the name or your OBJ file; Visual Studio will do it for
you. The ASM, RC and OBJ files all have the same name by default.

DO NOT REPEAT THIS FOR THE GLOBAL PROJECT SETTINGS.
DO IT ONLY FOR THE ASM FILE OR FILES, BY RIGHT-CLICKING ON THE FILE NAME(S).

It should not be necessary to put in include library
paths in the Link tab as they have been globally set in the
tools/options/directories/executables path.

Procedure to set up new installation of Visual Studio for MASM

1. Close all open workspaces in Visual Studio.

2. Click Tools . . . Options, on the top toolbar.

3. On the Directories tab, use the drop-down window
labelled ?show directories for.?

4. Select ?Executables? and add c:\MASM32\BIN.

5. Select ?Include files? and add c:\MASM32\INCLUDE.

6. Select ?Library files? and add:

c:\MASM32\LIB

c:\MASM32\M32LIB

7. For each project, if it was copied in from another
PC, the Custom Build settings should already be set. If not, use the
instructions above to set the custom build settings for each ASM file.
Posted on 2002-01-10 18:57:59 by sluggy
Wow, thanks for the detailed instructions.

Works like a charm! :alright:

Getting back to the original message of the thread, here's a link to directly download MS's free debbugger:

http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_4.0.18.0.exe

Seeing as how I am not going to be doing any kernal mode work in the future, the VC debugger will be good enough for me.
Posted on 2002-01-10 22:05:54 by Mecurius
Why didn't debug .exe with source mode
Posted on 2002-03-18 05:48:56 by zhongts
I'm using SoftIce 4.2.5 (with Numega DriverStudio 2.5) with Win2k and I have no problem. Pretty simple instalation, I dont know exactly, is the installer make some patches, but for me work fine. If you want to dig deep into system, there is no way of using something else.
Posted on 2002-03-18 09:13:18 by masquer