why not do it yourself at your code if you need? regards, Gang On Fri, Dec 5, 2008 at 10:58 PM, Johan Lantz <johan.lantz at genaker.net>wrote: > Hi > > I just spent some time on an issue. > > The user of my software was supposed to unload my dll completely after > disposing. However for some reason this mechanism did not work so the next > time he initialised my dll the static variables were unchanged from last > time. > > In one location I was counting on that a pj_pool_t* was set to NULL after > calling pj_pool_release(...) > > However this was not the case and there was a crash. > > One can argue that this is a design issue but maybe it could be a good idea > to reset the pj_pool_t pointer after releasing the pool since otherwise it > will continue to point to a valid memory address and problems can be > unessecary hard to debug. > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20081209/990869a6/attachment.html>
