If it operates successfully under WindDBG (or under any debugger) and not when used without that debugger, the underlying problem is typically related to a "race" between two events being processed by the code at the same time. One typically finishes before the other and therefore no bug generated. But sometimes the other one wins the race and causes a crash.
The debugger probably slows down the "bad" event of the two racing enough so that race no longer exists and so the bug is never recorded.
Of course that doesn't really help us much as we still have no idea what event is racing against what.
Please let us know if you ever get anything as I hate crashes and really want to remove all of them from Sigil as soon as they can be tracked down.
|