On Tue, March 15, 2016 00:17, Ross Finlayson wrote: > > I suggest looking at the various places - within your own application code - > where you might be deleting LIVE555 objects (using ?Medium::close()?), and > make sure that you?re not accidentally deleting them twice, or not deleting > them when the LIVE555 library code deletes them as well. (Note that, for > example, if you have a ?chain? of source objects: A->B->C (i.e., with B and C > being ?FramedFilter? subclasses), then only object C should be deleted > explictly; the LIVE555 code will automatically delete B and A for you.) > > Another thing I suggest is running your code under ?valgrind?. If - as I > suspect - the code is trying to access an object that has recently been > deleted, then ?valgrind? may be able to tell you specifically where in the > code the object was deleted.
We'll do these. Thank you for your suggestions. Bruno Abreu -- Living Data - Sistemas de Informação e Apoio à Decisão, Lda. LxFactory - Rua Rodrigues de Faria, 103, edifício I, 4º piso 1300-501 LISBOA Phone: +351 213622163 Portugal URL: www.livingdata.pt _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
