Topic: debuging DLL's and WME crash reporting (Read 4875 times)

SoundGuy · « **on:** December 26, 2007, 05:46:28 PM »

Hey
I've noticed that I can't debug crashes within my DLL now.
I want to see the stack calls and local variables in my DLLS so i run WME through my visual studio (as i did in the 1.7's of WME).
Before, in 1.7 when my DLL crash on access violation, i would go to the right point in the VC debugger, but now - the WME crash reporting tool takes over and i don't get to the VC at all.
I tried finding a way to disable the crash reporting, but looks like i can't do it when i'm using the wme in debug mode, without the need to build the whole game's packages, which is a major inconvenience when trying to debug...

Oded

Mnemonic · « **Reply #1 on:** December 26, 2007, 05:50:56 PM »

Try deleting or renaming the "wme_report.dll" file in WME's install directory.

SoundGuy · « **Reply #2 on:** December 26, 2007, 06:10:15 PM »

will do - on my next debugging session.

SoundGuy · « **Reply #3 on:** December 26, 2007, 06:10:45 PM »

but I would rather prefer there will be a checkbox for it rather then needing to rename the dlll ;-)

News:

Author Topic: debuging DLL's and WME crash reporting (Read 4875 times)

SoundGuy

debuging DLL's and WME crash reporting

Mnemonic

Re: debuging DLL's and WME crash reporting

SoundGuy

Re: debuging DLL's and WME crash reporting

SoundGuy

Re: debuging DLL's and WME crash reporting