Hi Yuriy, we both looked for a Radius leak a few months ago and couldn't locate one, so I would need a much more detailed report how to replicate the leak. Actually anybody using GnuGk can run a check for memory leaks: There is a tool called 'Valgrind' and its included with most Linux distributions. Simply compile a GnuGk debug executable and instead of running it as always "gnugk -c file.ini -t", you run it under Valgrind: "valgrind --log-file=vg.log --leak-check=yes gnugk -c file.ini -t" The you use GnuGk as usual and try to make all different sorts of calls that might produce a memory leak. After shutting GnuGk down (eg. with Ctrl-C), vg.log will contain a report with leaks. There will be a few harmless things, like memory allocated on startup and never released, but if you managed to trigger a real leak, it will be there, too, along the source line that allocated it. The only downside is that Valgrind will reduce performance dramatically, so you probably can't use this in a production environment. Regards, Jan Georgiewskiy Yuriy wrote: > Hi. > > There is memory leak steel exist somethere in radius support part. -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
