Skip to content

Commit

Permalink
Rework debugging check in BReferenceable.
Browse files Browse the repository at this point in the history
- If a BReferenceable object is deleted with a non-zero reference count,
  we now test to see if the object was allocated on the stack. If so,
  we don't flag a warning if the reference count is currently 1.
  • Loading branch information
anevilyak committed Dec 6, 2012
1 parent 36b2108 commit 4a5bcf0
Showing 1 changed file with 12 additions and 2 deletions.
14 changes: 12 additions & 2 deletions src/kits/support/Referenceable.cpp
Expand Up @@ -27,8 +27,18 @@ BReferenceable::BReferenceable()
BReferenceable::~BReferenceable()
{
#ifdef DEBUG
if (fReferenceCount > 1)
debugger("Deleted object which still had references.\n");
if (fReferenceCount != 0) {
// Simple heuristic to test if this object was allocated
// on the stack: check if this is within 1KB in either
// direction of the current stack address, and the reference
// count is 1. If so, we don't flag a warning since that would
// imply the object was allocated/destroyed on the stack
// without any references being acquired or released.
char test;
int64 testOffset = (int64)this - (int64)&test;
if (testOffset < -1024 || testOffset > 1024 || fReferenceCount != 1)
debugger("Deleted referenceable object with non-zero ref count.");
}
#endif
}

Expand Down

0 comments on commit 4a5bcf0

Please sign in to comment.