Anyone using CodeAnalyst with SETI app?

[Raistmer]

I tried to run pipeline simulation with SETI app but some exception occurs at loading time preventing to collect execution trace. The worst is the log windo fot trace collector module closing immediately after error so it's not possible to read where and what going wrong.  Anyone tried CodeAnalyst? Any comments? (I run profiling for AMD 64 Venice so vTune probably not an option).
(Time based and event based profiling sessions run just fine).

[Jason G]

I had a similar issue instrumenting for VTune.  I think for VTune the full instrumentation was attempting to instrument some kernel or C Runtime functions it shouldn't have been.  For VTune, and I don't know if this is possible on CodeAnalyst, the solution was to do custom instrumentation and deselect all functions beginning with an _underscore.

Jason

[Raistmer]

CodeAnalyst doesn't require any instrumentation but requires pdb-file with symbol names. If it's possible to exclude from debug info range of functions maybe it could be possible to check if this helps Probably it's possible to generate debug info only for modules under interest (actually only opt_sse2's functions needed).. will try to rebuild, thanx for idea