Closed Bug 663177 Opened 13 years ago Closed 13 years ago

GCRoot: sanity-check that 'this' is object's beginning

Categories

(Tamarin Graveyard :: Garbage Collection (mmGC), defect, P2)

Product:
Tamarin Graveyard
Component:
Garbage Collection (mmGC)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX
Milestone:
Q3 11 - Serrano

People

(Reporter: pnkfelix, Assigned: pnkfelix)

References

Details

(Whiteboard: WE:2873296)

Bug 663159 points out a problem with GCRoot and multiple inheritance; we will have to find a robust solution in the long term to that problem. But in the short term (ie for Serrano), we need to put in safe-guards to protect against new instances of the bug being introduced. That's what this bug is for.
Assignee: nobody → fklockii
Whiteboard: WE:2873296
Flags: flashplayer-qrb+
Flags: flashplayer-injection-
Priority: -- → P2
Target Milestone: --- → Q3 11 - Serrano
Summary: GCRoot: sanity-check that this is object's beginning → GCRoot: sanity-check that 'this' is object's beginning
This might work, but be wary -- a debug assertion could check that GCRoot's this matches the allocation start, but we have no way of being certain that the layout in non-debug (optimizer-enabled) builds will match that of debug builds. A "selftest" involving a compile-time assert might be doable?
Depends on: 663508
Abandoning this tack and instead taking the FixedMalloc::FindBeginning(this) approach; see Bug 664137.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.