Closed Bug 953316 Opened 12 years ago Closed 12 years ago

Beef up dumpObject output to include all object flags

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
minor

Tracking

()

RESOLVED FIXED
mozilla29

People

(Reporter: Waldo, Assigned: Waldo)

Details

Attachments

(1 file)

Not sure why we don't have these...
Attachment #8351604 - Flags: review?(bhackett1024)
Comment on attachment 8351604 [details] [diff] [review] objectflags-dump.diff Review of attachment 8351604 [details] [diff] [review]: ----------------------------------------------------------------- It's pretty easy for these to go out of phase. Maybe add a mechanism to test for unrecognized flags in the dump functions and print some "unknown flag" message or something to make this more obvious? Though just this is fine.
Attachment #8351604 - Flags: review?(bhackett1024) → review+
I added a comment by the objectflags enums that people need to keep the list synced with JSObject::dump. So long as the flags are handled one at a time in JSObject::dump, doesn't seem there's a better way to do it. We could perhaps have Shape::dumpObjectFlags or something to at least move it into Shape's domain, but I didn't want to rathole too much here. :-) https://hg.mozilla.org/integration/mozilla-inbound/rev/d574815fe704
Target Milestone: --- → mozilla29
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Thank you.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: