Automatically Handle Failed Asserts in Debug Builds
As of 2004-12-8, it is now possible to automatically handle failed asserts in debug builds of Mozilla for Windows.
The handler receives the assert string, and sequentially attempts to match each word in the string (left to right) to registry DWORD names from
HKCU\Software\mozilla.org\windbgdlg. At the first match, it will take the action specified by the DWORD's value.
The valid values are:
Note that you can also force windbgdlg to prompt, by setting a value of
To "comment out" a value, set its value to
As an example, consider the following failed assertion:
ASSERTION: no document: 'mDocument != nsnull', file d:/cvs-1.11.4/mozilla/content/xul/content/src/nsXULElement.cpp, line 3173
(note that I have my source tree in d:/cvs-1.11.4/mozilla)
If you have a DWORD in
HKCU\Software\mozilla.org\windbgdlg\ named "d:/cvs-1.11.5/mozilla/content/xul/content/src/nsXULElement.cpp," (WITH the comma - matches are whole-word only) and value
0x5, the assert would automatically be ignored. If you also had a DWORD named "3173", it would have no effect here because the handler stops comparing values at the first match.
Note that double quotes which delimit an item (") are ignored in value names and the assertion string, so
silly will both be matched by a value named
"silly", will only be matched by a value named
"silly", since the quotes are internal to the string.