Hi George,
On Tuesday, August 16, 2005, at 07:17AM, George Birbilis <email@hidden> wrote:
>tell the compiler to generate a .map file (text, readable), then you can use
>drwatson.exe or similar to see where it crashed (the problem maybe elsewhere
>though)
I have done this, but after the app crashes, clicking on DrWatson says no faults were detected. Am I using that tool wrong?
>
>better add logging calls in your code to write to a file (or to use
>WriteDebugStr or similar to send debug strings to a debug messages
>display/console like the free one from www.sysinternals.com). Then you see
>the execution path it took
There are a lot of places this might fail. I'm going to try it anyway, but if you have any other suggestions, please let me know!
Aren't there performance monitoring apps like CHUD for Windows? Can anyone recommend one?
>also use assertions to check for expected conditions at proc entry and exit
>and if they fail the assertion will fire and let you know. Then at
>deployment you tell compiler to ignore assertions
Doing that already ;-)
-Chilton
(fish out of water)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-api/email@hidden
This email sent to email@hidden
