On 4/20/06, Colin Whittaker <[EMAIL PROTECTED]> wrote: > Now for my real question,... > Is there some documentation on how the su memory allocation routines > keep track of memory ?
There is a short introduction text in http://sofia-sip.sourceforge.net/refdocs/su/group__su__alloc.html There seems to be nothing about preloading and stack-allocated homes there. What is your opinion on the text, should there be something more in the tutorial? > I get the idea of the home object. I'm not sure I understand how the > sub_alloc works. What sub_alloc() does? It 1) resizes the hash table (su_blocks_t) if needed 2) allocates a memory block either using a) "preloaded" memory b) calloc() or c) malloc() 3) initializes cloned subhome 4) adds the block into hash table, hash table also keeps tab of the block size and whether the block is a subhome or not > With a typical nua implementation, are there more than the nua and su > home objects ? > Would I expect to see all other allocations as sub objects to these two ? msg_t is important, too. > Any idea's on how to track this down would be helpful. Tracking a memory > leak is quite tricky. I added the handle-level debugging output to nua, as explained earlier. Then there are some debugging output from nta, for instance, keeping tab of transactions. We have used valgrind, too, but I must admit that using homes make valgrind much less useful. --Pekka -- Pekka.Pessi mail at nokia.com ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Sofia-sip-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
