Closed
Bug 229972
Opened 21 years ago
Closed 21 years ago
mDocShell in LayoutDebuggingTools is null
Categories
(Core :: Layout, defect, P2)
Core
Layout
Tracking
()
VERIFIED
FIXED
mozilla1.7alpha
People
(Reporter: bernd_mozilla, Assigned: dbaron)
Details
(Keywords: crash, Whiteboard: [patch])
Attachments
(1 file)
|
1.18 KB,
patch
|
bryner
:
review+
bryner
:
superreview+
|
Details | Diff | Splinter Review |
1. build mozilla with the layoutdebugger extension in debug mode
2. launch mozilla -layoutdebug
3. select Dump->Webshell
4. deref a Null Pointer at
http://lxr.mozilla.org/seamonkey/source/extensions/layout-debug/src/nsLayoutDebuggingTools.cpp#366
5. launch your prefered debugger to catch the crash
===> the whole dumping is currently broken
|
Assignee | |
Comment 1•21 years ago
|
||
|
|
Assignee | |
Comment 2•21 years ago
|
||
Comment on attachment 138661 [details] [diff] [review]
patch
I guess I was relying on something else having already QI'd gBrowser.docShell
to nsIInterfaceRequestor. the contentWindow binding at
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/xpfe/global/resources/conte
nt/bindings/browser.xml&rev=1.29&mark=212-214#212 does what I need.
Attachment #138661 -
Flags: superreview?(bryner)
Attachment #138661 -
Flags: review?(bryner)
|
|
Assignee | |
Updated•21 years ago
|
Assignee: nobody → dbaron
Severity: normal → critical
OS: Windows XP → All
Priority: -- → P2
Hardware: PC → All
Whiteboard: [patch]
Target Milestone: --- → mozilla1.7alpha
|
|
Assignee | |
Comment 3•21 years ago
|
||
|
||
Updated•21 years ago
|
Attachment #138661 -
Flags: superreview?(bryner)
Attachment #138661 -
Flags: superreview+
Attachment #138661 -
Flags: review?(bryner)
Attachment #138661 -
Flags: review+
|
|
Assignee | |
Comment 4•21 years ago
|
||
Fix checked in to trunk, 2003-01-08 15:57 -0800.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
|
||
Updated•7 years ago
|
Product: Core → Core Graveyard
|
||
Updated•7 years ago
|
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•