Trying out Trial of Team suite/edition problem profiling

I'm investigating the profiling capabilities of 2005 team suite for our development team.

I've run into a couple of issues though. I'm trying to profile a C++/MFC app.

First I'm getting a mixed message when I try and launch my app for instrumented profilng. I get the following message.

Warning VSP2005 : Internal Instrumentation Error: The object '\LPWindowTest\Source\Windows\zlibstat.lib(.\zlibstat\adler32.obj)' was built without debug information.

Is this a warning, that is I can continue or an error Is there anyway to specify libraries to ignore for profiling/instrumentation

Secondly I get another error

Error VSP1014 : Code discovery analysis failed during processing image '|2'.

Is this related to the first or is something else going on If something else I'm at a lose on what it is I should do.

Finally is there a good place of documentation for the various settings/flags etc. So far I'm unimpressed with the lvl of documentation but perhaps I'm not looking in the right place.

Thanks much

James

Answer this question

Trying out Trial of Team suite/edition problem profiling

deepshikha

James,

I'd agree that the error message is a little uninformative in this situation. It's something that we're working on for the next release. The error that you are seeing is due to the fact that your application has a statically linked library which there is no pdb for. We user the pdbs for instrumentation, so we can't instrument the binary unless we get symbols for that library.

Thanks,

Ian
Trying out Trial of Team suite/edition problem profiling

Answer this question