Nightinggale
Deity
- Joined
- Feb 2, 2009
- Messages
- 5,385
In theory you could run the game in a debugger. However to make that useful, you would need to use a debug DLL, which is dead slow. Also it's kind of useless unless you know how to use a debugger. Even worse: in this case I did catch the crash in the debugger and all it said was "crash inside exe file". I had to be super creative to at least get it to reveal it being audio related.Any way for us with frequent crashes to have some app in background that may log the crash for more info to give to the team?
Looks like all the crashes we have had with 4.0 and later have been the DLL feeding invalid data to the exe and then the exe crashes. However without the source code for the exe, a crash there doesn't really help much in terms of pinpointing the cause of the crash. I have plans for getting the DLL to verify all sorts of xml data setup and presence of files, but that's unlikely to be part of the next release due to how long it takes to make that properly.