Closed Bug 304237 Opened 20 years ago Closed 20 years ago

Enable xpcom under windows debuggers to filter assertions the way it does without a debugger

Categories

(Core :: XPCOM, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: timeless, Assigned: timeless)

References

Details

(Keywords: fixed1.8)

Attachments

(1 file)

to enable this feature, set XPCOM_DEBUG_DLG=1, or if you're already in the debugger, just poke the static to 2.
Comment on attachment 192308 [details] [diff] [review] let debugger users benefit from windbgdlg if they want to why 2?
Attachment #192308 - Flags: review?(dougt) → review+
0 is used by the variable to mean it hasn't checked the env var, 1 means that the user had the env var unset or set to 0, 2 means the user set the env var to 1. i'm just abusing the fact that static means things start at 0.
Status: NEW → ASSIGNED
Comment on attachment 192308 [details] [diff] [review] let debugger users benefit from windbgdlg if they want to this is localized windows code that is only used by debug code and only affects users who are in debuggers. the benefit is that users in debuggers can choose to ignore certain assertions. for its audience this is a good reward. for everyone else this is basically no risk.
Attachment #192308 - Flags: approval1.8b4?
Comment on attachment 192308 [details] [diff] [review] let debugger users benefit from windbgdlg if they want to mozilla/xpcom/base/nsDebugImpl.cpp 3.11
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Attachment #192308 - Flags: approval1.8b4? → approval1.8b4+
Keywords: fixed1.8
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: