Re: Could not debug the code using visual studio
- From: "Oleg Starodumov" <com-dot-debuginfo-at-oleg>
- Date: Wed, 27 Dec 2006 10:46:51 +0200
I have a VC project for my tool which is using Makefle for compilation of
code .Make file using cl.exe for compiling the code. I can successfully
compiled tool's code using Makefile. While linking using link.exe i am
getting following warning
"mylib.lib(mywrapper.obj) : warning LNK4204:
'C:\ntregres_raj_sln\Acess\tools\src\np_sync\vc70.pdb' is missing debugging
information for referencing module; linking object as if no debug info"
Note: My current configuration of the project is DEBUG and during compiling
the tool i am using /Zi, /Z7 and /FD options.
Here the problem is with the library mylib.lib. Probably it was compiled with /Zi option,
but the resulting .pdb file is not available at the moment of linking.
When compiling this library, either use /Z7 option, or use /Zi and /Fd to change
the default name of the .pdb file to something library-specific (e.g. mylib.pdb).
After this warning my executable is prepared but i could not debug this
executable. Debug window showing following
'np_sync.exe': Loaded
'C:\ntregres_raj_sln\Acess\tools\src\np_sync\np_sync.exe', Symbols loaded.
Symbols for the executable are loaded, so it should be possible to debug it
(unless most of its code is located in mylib.lib).
What happens if you start debugging with F10? Will you be able to step
through the source code?
If you set a breakpoint in the entry point function, will it be hit?
--
Oleg
[VC++ MVP http://www.debuginfo.com/]
.
- Prev by Date: Re: Listing & debugging explicitly loaded DLLs via LoadLibrary
- Next by Date: Re: Dr Watson is locking up my computer
- Previous by thread: Listing & debugging explicitly loaded DLLs via LoadLibrary
- Next by thread: Re: Dr Watson is locking up my computer
- Index(es):
Relevant Pages
|
