>Hi everybody,
>
>This is not actually a .NET question. Quite often when a Windows application crashes (in my case it was C++ app), it gives an ability to debug it in Visual Studio. But how exactly should I debug it and is it useful at all to answer yes on the debugging dialog?
>
>Say, this is what I see in the middle of the stack:
>
> mfc100.dll!COleDispatchImpl::Invoke(long dispid=49, const _GUID & riid={...}, unsigned long lcid=1033, unsigned short wFlags=4, tagDISPPARAMS * pDispParams=0x00000001, tagVARIANT * pvarResult=0x00000000 Empty, tagEXCEPINFO * pexcepinfo=0x0018f228, unsigned int * puArgErr=0x00000000) Line 1507 + 0x10 bytes C++
>
>
>Does it help me in any way? Is there a way to see the actual code that led to the error?
>
>Thanks in advance.

LOL at Viv's answer, it was spot on.

Basically unless you are really good at assembly language, the BIOS, Win32 and have TONS of time to waste. Don't bother with it.

Unless you have the source code, you would have to reverse engineer most of what it will show you.