qom: Assert that objects being destroyed have no parent
QOM reference counting bugs are often hard to detect, but there's one kind of bug that's easier: if we are freeing an object but is still attached to a parent, it means the reference count is wrong (because the parent always hold a reference to their children). Add an assertion to make sure we detect those cases. Signed-off-by: Eduardo Habkost <ehabkost@redhat.com> Message-Id: <20201215224133.3545901-3-ehabkost@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
parent
08bdf5d44f
commit
63f957ac96
@ -685,6 +685,7 @@ static void object_finalize(void *data)
|
|||||||
object_deinit(obj, ti);
|
object_deinit(obj, ti);
|
||||||
|
|
||||||
g_assert(obj->ref == 0);
|
g_assert(obj->ref == 0);
|
||||||
|
g_assert(obj->parent == NULL);
|
||||||
if (obj->free) {
|
if (obj->free) {
|
||||||
obj->free(obj);
|
obj->free(obj);
|
||||||
}
|
}
|
||||||
|
Loading…
Reference in New Issue
Block a user