Tip: ulimit -s 240, or freeswitch fork and execv out from under valgrind.
/b On Mar 16, 2009, at 11:01 PM, Chris Fowler wrote: > > >>> Anthony - valgrind --tool=memcheck --log-file=vg.log --leak- >>> check=full --leak-resolution=high --show-reachable=yes /path/to/ >>> freeswitch -vg > > > Nothing got logged, here's the output. Did I invoke valgrind > incorrectly? > > ==32545== Memcheck, a memory error detector. > ==32545== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et > al. > ==32545== Using LibVEX rev 1658, a library for dynamic binary > translation. > ==32545== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP. > ==32545== Using valgrind-3.2.1, a dynamic binary instrumentation > framework. > ==32545== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et > al. > ==32545== For more details, rerun with: -v > ==32545== > ==32545== My PID = 32545, parent PID = 32511. Prog and args are: > ==32545== /usr/local/freeswitch/bin/freeswitch > ==32545== -vg > ==32545== _______________________________________________ Freeswitch-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
