Print address of XPTCStub with nsXPCWrappedJS, to help debugging

RESOLVED FIXED in mozilla8

Status

()

Core
XPConnect
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: azakai, Unassigned)

Tracking

unspecified
mozilla8
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [inbound])

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Created attachment 549002 [details] [diff] [review]
patch

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 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

6 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]
http://hg.mozilla.org/mozilla-central/rev/b9e9b5a4959a
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla8
You need to log in before you can comment on or make changes to this bug.