Hey Jack,
     First I thought I'd give you a heads-up for the future. The
profiler_hst sample code that you've compiled, and the other profiler
samples in the SDK, don't ship with Whidbey--the CLR Profiler sample
(http://www.microsoft.com/downloads/details.aspx?FamilyId=86CE6052-D7F4-4AEB
-9B7A-94635BEEBDDA&displaylang=en) demonstrates all the same things, so
those smaller samples became redundant. Also, again just a heads-up, the
behavior of the profiling API with Whidbey has changed to such an extent
that if you will need to make some updates to your tool for it to continue
working against Whidbey. The profiling docs in the Whidbey Beta 1 SDK have
details about exactly what those updates would be.

    However back to debugging the problem at hand. I did a quick search of
the hst_profiler sample, and that message string occurs in only two places
in profilerinfo.cpp. If it's a pretty consistently-reproducible issue, I'd
recommend setting breakpoints at both of them to start with and try to
figure out which functions are having problems getting information. Then
you could set conditional breakpoints to fire when just those functions are
being processed to walk through and isolate where the failure is coming
from. Debugging profilers is a little tricky because of the whole
environment-variable-activation thing. The VS Whidbey debugger has some
neat features that let you set the environment of the target process which
makes that a LOT easier, but if you don't have Whidbey one relatively
simple workaround is to put a long sleep in your code--either the profiler
Initialize callback or the target process code, it doesn't really
matter--and attach a debugger during that sleep. (If you're attaching VS,
make sure you pick "native only" rather than "auto.")

HTH,

Jonathan

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

08:25:56 GMT)

cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!news.glorb.com!postnews1.google.com!not-for-mail