This is just a resurrection of #813. I had to move the writedump methods to XBApplicationEx.cpp because they wasn't caught in thread.cpp.
I've added quite some code duplication in XBApplicationEx.cpp because I didn't want to introduce new methods or goto's. Please comment if there's a better way.
@jimfcarroll I've added some minidumps to thread.cpp as CrystalP did: wsoltys@fe6cc74 (somehow I can't see that yet in the pr). Do I still need the own catch routine there?
I tried to take a quick look but didn't get far enough to understand more than what you're trying to do. I should be able to take a closer look over the weekend.
Just so you know, when I was working with CrystalP I added the abstract Exception handling so that you could plug in logging (minidump, etc) in the LogThrowMessage of the Win32Exception. I never heard back from him as to whether that worked for him.
Thanks for looking into it. I forced a division by zero in a thread to test it but it was only caught in the default handler (...). After calling win32_exception::install_handler(); in CThread:action (see 1b436e6) it worked at least with the two catch's I've added.
I want to do the same thing. where is a good place for the divide by zero?
MP3Codec.cpp comment l60 and play a mp3 file :)
note that for debugging the catch's in xbapplicationex are ifdef out that the ide catches the exception.
[WIN32] added new EXCEPTION_POINTERS member in exception handling.
[WIN32] move minidump writing function to Win32Exception
Use the Exception abstractions to manage the handling of platform spe…
okay, squashed and rebased with jcarrolls changes.