WinDbg Problem - Symbol Path

[raleeper]

WinDbg is giving me this error message:

   Your debugger is not using the correct symbols

   In order for this command to work properly, your symbol path must point
   to .pdb files that have full type information.

   Certain .pdb files (such as the public OS symbols)
   do not contain the required information. Contact
   the group that provided you with these symbols if
   you need this command to work.

   Type referenced: cposy

But WinDbg/file/symbol Path  shows (the symbol path to be) h:\lfw.

h:\lfw contains:

LFW.ASM         20494     06/17/07
LFW.EXE         15151     06/17/07
LFW.ILK         35732     06/17/07
LFW.LST         29668     06/17/07
LFW.OBJ        240985     06/17/07
LFW.PDB        336896     06/17/07

cposy is a symbol (.DATA?/cposy   DD   ?) I used 5 or 6 assemblies ago but then discarded.

Can anyone suggest how I can get around this - and what is going on?

Thanks.

[raleeper]

Fixed it.

And I see I need to be less quick to ask for help.

Thanks.

[raleeper]

The problem is back.  The problem wasn't showing up and I wrongly assumed I had done something to fix it.

Everything is the same as described below, except now the type referenced is "Your", which is probably a remnant of a failed assembly where I omitted a quote mark or a semicolon.

Can anyone suggest what I might be doing wrong or what I can try to fix this?

Thanks.

[herge]

 Hi:

Check environment variables PATHEXT and add
.PDB;
to it. It's in the Control Panel.[sytem]{Advance]
Just because it's being in the Path don't mean
winDbg will see it.

[redskull]

most every setting in WinDBG is part of a save-able 'workspace', which you have to reload everytime (or change the default one).  So don't assume just because you changed a setting once means it will stay that way the next time you load it up.  I wrote some stuff awhile back if you're interested

-alan

http://www.masm32.com/board/index.php?topic=4741.0

[ToutEnMasm]

Hello,
To help configuring winhelp at start,OSR online have a tool to launch it
http://www.osronline.com/
My ide have also a tool environ.exe that work  with  .pro textfile.The tool launch winhelp in windows with the needed parameters  in the dos environement (who can be modified in the text file .pro) .
Using the save workspace of winhelp offers many inconvenient.The first is a mixed soap of all needed path,find the good!.
note: files .pro must be associated with environ.exe

[herge]

 Hi ToutEnMasm

Have downloaded environ.exe
[bugbug + lirepro]
I can't run the batch file pdb.bat it's
looking for LIB files on my C drive.
My C drive is kind of maxed out so
I usually keep most things on the
F drive. Am also seeing a lot of
windows which I think is a Microsoft
Crash notice but I am not really sure.
[transparent bug]
I changed refernces of C to F
in DEBUG.PRO

[ToutEnMasm]

Hello,
Here is the compiled file environ.exe and a .pro file.
Make an association (in the file explorer ) between extension .pro and environ.exe (you must give the place of environ.exe,masm32 for example).The icone of .pro can be change to a tree.
In the .pro ,Verify the path to windbg.

programme:C:\Program Files\Debugging Tools for Windows\windbg.exe
;le programme a éxécuter,vérifier le chemin ou changer de debugger

Place the .pro in the directory of the source asm.
Modify the name of the .exe .

option:editmasm.exe

Doucle clic the .pro,windbg must be launch.All sources files and compiled files of the project are supposed to be in the same directory.If not,modify this or the paths in the .pro following the windbg help.







[attachment deleted by admin]

[herge]

 
Hi ToutEnMasm:

[debug.pro]
Windbg starts and is looking for Editasm.exe.
I am having trouble associating PRO with
environ.exe

[ToutEnMasm]

You must replace editmasm.exe     in  myprog.exe

;option:-c
option:-c ".sympath+ SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols"
;---------------- mise a jour des symboles windows !!!-------------------------------
;option:-c "$$><cheminTextePro\pro.txt"
;Load Source File ,charger un fichier source,plusieurs commandes ajouté ; ????

option:editmasm.exe                       

You can also put a shorcut on environ.exe in your sendto path

C:\Documents and Settings\username\SendTo\environ.lnk

[herge]

 
Hi ToutEnMasm:

Things are coming along slowly.
  I have down loaded Editmasm.
It does not like my Project names.
I think I can compile Projects because
I see a blue fini message.
I can open my source files.
I don't think I have set up Editmasm
right.
Environ is getting to Windbg thou.

[ToutEnMasm]

For projects,you must create them with editmasm.
Files names must be in dos convention (max 8 lettrers + 3 lettres max for extension),in the same directory.
Use the file open dialog box and add all the files you want to see in the project (multiple selections can be done).
Use "gestion des projets"->"creer ou modifier" ,answer to the questions
    ------ type of compile file to create
    ------ names of asm  to compile     (two differents are possible)
    Optionnal create a menu for compile (don't use that to start)

Be sure to have used the instal.bat for install.
To start you can used "gestion des projets"->"Modeles standard"--- choose "sans fenêtre",this will help you starting.

[herge]

Hi ToutEnMasm:

I am trying to compile Floatz.asm
but I am getting Minus.asm.

[attachment deleted by admin]

[ToutEnMasm]

Hello,
enter in Use "gestion des projets"->"creer ou modifier".There is a listbox,double clic on the name of asm you want to compile.The name of this asm must appear in the project dialog under "premier source"

[herge]

Hi ToutnMasm:

I can only compile Minus.ASM in fact it's the ONLY
file i can compile.
It's not a clean compile a Macro is invoking two
exception procedures which I can not find i
have even scanned for the Proc names and did
not find them.

\masm32\bin\ml.exe /c /coff /nologo /Zi /Zd /Zp4 minus.asm
F:\masm32
Assembling: minus.asm
minus.asm(52) : error A2006: undefined symbol : AddVectoredExceptionHandler
XPEXCEPT(2): Macro Called From
  minus.asm(52): Main Line Code
minus.asm(52) : error A2006: undefined symbol : RemoveVectoredExceptionHandler
XPEXCEPT(8): Macro Called From
  minus.asm(52): Main Line Code


????????????????????????????????????????????????

Minus.asm is always premier source.
When I do a new Project it takes for ever to
point to F:\masm.
It usually does not like my project names.