Environment versions
Network:
Windows 2003 Server
>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?
Not if you wish to retain your sanity :-}
>
>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.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only