[Valgrind-users] refcounters, cycles and leak detection.

[<sh...@ne...>]

Is there any way to make valgrind detect that there's a cycle?  IE we 
(like many others) have a reference counted smart pointer in our 
application library, which gets used all the time.  As you might guess, 
you have to be careful to avoid cycles, else you create things that, 
once you get rid of the external handle, their existing handles to one 
another will prevent their deletion. 

I created a very trivial test of this, and it didn't seem to detect that 
I had leaked the 2 objects (A had nothing but a handle to B, B had 
nothing but a handle to A).  I guess this is because there ARE valid 
references, but I'm just wondering if there's any way to get valgrind to 
detect this?

Chris