[reSIProcate] More Heap corruption..

[Matthias Moetje - TERASENS GmbH]

Byron, Scott,
 
thanks very much for your replies. I'm using the
InMemoryRegistrationDatabase. 
 
I understand that the list elements are'nt pointers, but the std::list
implementation
calls delete two times and if I skip the first, the heap corruption does
not occur.
 
I stepped through all of the list implementation code when assigning,
but I never
passed the Uri's copy constructor, shouldn't this have occured?
 
One difference to repro is that I am creating the
InMemoryRegistrationDatabase
with "new" (so it is created on the heap itself) and keep a pointer to
it as long
as the session is running. Could this be the reason for the problem?
 
Matthias
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060608/febbb94e/attachment.htm>