hendricks266 43eb98fdec Extend ebacktrace in two ways. ... 1. The application must specify its proper name and technical name. Instead of eduke32_or_mapster32.crash.log, we now have eduke32.crash.log and mapster32.crash.log. 2. The exception handler will display a message box informing the user of a crash and requesting they send in the crash log. The box has three options: "Quit", the DLL's current behavior, "Continue", which passes the exception to the next handler, and "Ignore", which resumes execution immediately. These should allow the user to skip bogus exceptions picked up by ebacktrace, such as one I get with my laptop that causes EDuke32 no issues. git-svn-id: https://svn.eduke32.com/eduke32@4538 1a8010ca-5511-0410-912e-c29ae57300e0		2014-07-06 22:38:02 +00:00
..
win32	Extend ebacktrace in two ways.	2014-07-06 22:38:02 +00:00
win64	Extend ebacktrace in two ways.	2014-07-06 22:38:02 +00:00