Vtune having exception

[prokash]

I just downloaded Vtune Amplifier, configured ( or selected the tab for system profile). Profiled it with basic hotspot anlysis ( this is allowed for the config type "system profile").

It gives exeception when it tries to writeout the result. I've windbg hooked up, so if I say gh it crashes.

Why it is crashing??

The context is partially valid. Only x86 user-mode context is available.

WOW64 breakpoint - code 4000001f (first chance)

First chance exceptions are reported before any exception handling.

This exception may be expected and handled.

00000000`0ee429f4 cc int 3

32.2: kd:x86> gh

The context is partially valid. Only x86 user-mode context is available.WOW64 breakpoint - code 4000001f (first chance)First chance exceptions are reported before any exception handling.This exception may be expected and handled.00000000`0ee429f4 cc int 332.2: kd:x86> gh

[Peter_W_Intel]

Are you using latest VTune Amplifier XE 2011, Update 7?

If you want to do system wide profiling, please don't doit under user-mode sampling data collection (Hotspots, Concurrency, LocksAndWaits analysis), please do it under HW event-based sampling collection - like as lightweight-hotspots, and other predefined analysis types for your running processor.

Regards, Peter

[SergeyKostrov]

Quoting prokash

...
WOW64 breakpoint - code 4000001f (first chance)

...

This is what 'ntstatus.h' Win32 API header file "says" about thecode 4000001f:

// MessageId: STATUS_WX86_BREAKPOINT
//
// MessageText:
//
// Exception status code used by Win32 x86 emulation subsystem.
//
#define STATUS_WX86_BREAKPOINT ((NTSTATUS)0x4000001FL)

Sorry, but it isunclear why the exceptionhappened...

[prokash]

Thanks Peter!

Sorry for being late to respond...

I think the trail version has some exceptions. If I boot with BCD debug enabled, and run some sample tests ( at the collection time) it breaks into debugger. If I boot with normal boot option, then exception is absorbed...

Thanks

-pro

[Bernard]

Your code is executing 0xcc instruction thus trigerring debugger breakpoint exception.Please post the full call stack.It is unknown why code path is executing int3 instruction.Sometime 0xcc is used as a padding for hot patching at runtime.