Closed
Bug 674800
Opened 13 years ago
Closed 13 years ago
Print address of XPTCStub with nsXPCWrappedJS, to help debugging
Categories
(Core :: XPConnect, defect)
Core
XPConnect
Tracking
()
RESOLVED
FIXED
mozilla8
People
(Reporter: azakai, Unassigned)
Details
(Whiteboard: [inbound])
Attachments
(1 file)
|
669 bytes,
patch
|
mrbkap
:
review+
|
Details | Diff | Splinter Review |
The attached patch prints out the XPTCStub's address when printing the nsXPCWrappedJS. This helps in debugging in situations where one might want to use the address of the stub and not the nsXPCWrappedJS itself.
Attachment #549002 -
Flags: review?(mrbkap)
|
||
Comment 1•13 years ago
|
||
Comment on attachment 549002 [details] [diff] [review] patch Only thought is that it might be more clear to add a "stub at" annotation so you don't have to remember which address is the wrappedJS vs. which is the stub each time. r=me either way if you prefer it this way strongly, though.
Attachment #549002 -
Flags: review?(mrbkap) → review+
|
Reporter | |
Comment 2•13 years ago
|
||
http://hg.mozilla.org/integration/mozilla-inbound/rev/b9e9b5a4959a I prefer the shorter version, since these logs get extremely long as it is.
Whiteboard: [inbound]
|
||
Comment 3•13 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/b9e9b5a4959a
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla8
You need to log in
before you can comment on or make changes to this bug.
Description
•