Closed Bug 412905 Opened 17 years ago Closed 8 years ago

Note NS_DebugBreak_P() in Linux debugging FAQ

Categories

(Developer Documentation Graveyard :: General, enhancement)

Product:
Developer Documentation Graveyard
Component:
General
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: matt, Unassigned)

Details

(Whiteboard: u=mozdev p=0 c=Platform) 

Under section 19, "How can I debug race conditions and/or how can I make something different happen at NS_ASSERTION time?", it should note that you can start Mozilla/Firefox/etc under gdb and set a breakpoint for NS_DebugBreak_P() to break at assertions *and* warnings without having to throw a signal.  I tried XPCOM_DEBUG_BREAK=suspend, but

1) That didn't catch warnings.

2) Every time I tried to "continue" it would immediately stop again because of the STOP signal that had been sent; breaking at NS_DebugBreak_P() avoids this problem
Product: mozilla.org → Websites
The www.mozilla.org site should no longer host documentation.  If there is still a need for this it should be added to MDC.  Moving to Mozilla Developer Center product for discussion.
Component: www.mozilla.org → Documentation Requests
Product: Websites → Mozilla Developer Center
QA Contact: www-mozilla-org → doc-request
Version: other → unspecified
Component: Documentation Requests → Documentation
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
Whiteboard: u=mozdev p=0
OS: Linux → All
Whiteboard: u=mozdev p=0 → u=mozdev p=0 c=Platform
I don't know if this document still exist anywhere, so I'm WONTFIXING this bug.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.