Re: Trying out Team suite for VS2005, help with profiling (documen
"James B." <JamesB@discussions.microsoft.com> wrote in message
news:87094762-95EA-49DF-B4E9-862A2D1C7283@microsoft.com...
I tried to respond to this but looks like it didn't go through (waited
about
15 mins).
I realized looking through my first post I did leave out some info that
might be helpful.
First off I mentioned dlls, but for the main app I want to profile we use
static linking, so it seems that if I instrument something it has to be an
.exe unless somehow I can specify .obj to instrument?
That's correct. You instrument whole modules - EXEs or DLLs. There's no
way to instrument only part of a module.
I will check out the links you gave and see if that helps.
Regarding my error/warning messageas. I get several of these warnings ...
Warning VSP2005 : Internal Instrumentation Error: The object
'\LPWindowTest\Source\Windows\ThirdParty\quicktimesdk\libraries\qtmlclient.lib(\qtml\buildresults\NoSym\obj\qtmlClientPublic\Toolbox\ClientToolboxAPI.obj)'
was built without debug information.
You've linked a mixture of object files, some compiled with debug info and
some without. note that you can generate debug info for release builds - I
think that's the default for new projects created with VC2005, but probably
not for projects migrated from 2003 (or earlier).
So my understanding is these warnings aren't causing my error, This is
the
error message I"m getting.
c:\LPWindowTest\Source\Windows\UnicodeRelease\LoggerPro.exe -->
c:\LPWindowTest\Source\Windows\UnicodeRelease\LoggerPro.exe
Error VSP1014 : Code discovery analysis failed during processing image
'|2'.
I think those warnings are related - I'm not sure if the profiling tools are
prepared to deal with an image that only has partial information in the PDB
file. I'd try getting everything built with debug info to see if that
doesn't take care of both the warnings and this error.
I'm not sure if the above line with the path info is part of the error
message or not ( perhaps just the Error VSP1014 is the error line.)
So, are the first things really just warnings I can ignore?
Any idea what the error message is or how I would resolve it? I'm really
finding the documentation on the profiling to be very sparse.
Would I be better of dynamically linking (I can do this when profiling)
You'd have better control over what parts are profiled if you broke the code
up into DLLs. If that's an option for you, it's probably worth trying out.
Again thanks for all your help
No problem!
-cd