Quote Originally Posted by Moorea View Post
thx, updated the faq some more

about the crash I can somewhat reproduce it by

- starting 2 wow windows on main pc
- starting mojo (from VC debugger)
- starting mojo on 2nd pc

"doing something else" on main pc (like typing in the faq)

earlier; before I cleared my settings, it was happening all the time at each launch of the 2nd mojo but I also had the 2 wow windows logged in and playing; so I'm not sure exactly which parameter makes it harder to reproduce - have you seen that error before - is it useful I try to reproduce it ?
The only crash I ever see is when I debug a release build. The debugger crashes at a certain place in the source. I think it's a bug in the debugger.

The program shouldn't be able to crash because it has a "last resort" crash handler that should intercept any exception. Worst case, in the debugger, the program should generate an exception. Outside the debugger, the program should show a dialog box asking the user to send me a minidump.

The code that displays the WoW icons is unfinished and it's quite possible it has a null pointer error in it or something like that. But it shouldn't make the debugger crash. It should just generate an exception.

To switch to a debug build, go to Build : Configuration Manager : Active Solution Configuration.