WinDbg shows improper crash point

[Dhamoscm]

Hi,

I am using WinDbg as my default debugger for my Multithreaded VC++ application.

Crash happens in COleDateTime object when it is assigned with 0x793406fff (maximum value).

But WinDbg does not shows this exact crash point and shows different functions at different times.E.g. Sometimes it shows in WaitforSingleObject, Sleep, etc.

Note: I have downloaded the complete symbols for WinXP platform.

I am interested to know why this type of behavior happens in WinDbg. Solving this will help us to resolve many problem quickly.

Regards,

Dhamo.

[MANEMAN]

Hi there Dhamo.

I am interested to know why this type of behavior happens in WinDbg.

It would be foolish of us to think that we could easily explain the behaviour of WinDbg here on a forum.

Firstly of course because so much is written on the subject in other places that we would merely be duplicating that which is already written.

Try this link: http://msdn.microsoft.com/en-us/library/ms164746.aspx which you will realise is a duplication of a link given to you earlier today at "The Code Project" when mysteriously your name was Dhamuuuuu.

I note that John Simmons gave you an answer and the link, and you have not yet thanked him for his help, or been forthcoming of any information as to whether it was useful to you.

Perhaps out of decency to him we should await this happening before we continue on this particular forum.

John.

Edit: Rule #1 - Never try to outsmart a smartass.

[bludgard]

Movin' right along....