-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/10/2014 4:40 a.m., Steve Hill wrote: > On 30.09.14 16:13, Amos Jeffries wrote: > >>> I'm trying to figure out if there's a way of convincing >>> valgrind to dump info about all the currently allocated memory >>> while the program is still running - there would be a lot of >>> legitimate stuff in the report, but hopefully a few hundred MB >>> of memory that shouldn't be there would stick out like a sore >>> thumb. >> >> That would be lovely. If you can find it I'd like to know too >> :-) > > su -s /bin/bash squid valgrind --vgdb=full --error-limit=no > --tool=memcheck --leak-check=full --show-reachable=yes > --leak-resolution=high --num-callers=40 squid -f > /etc/squid/squid.conf -N > > Do whatever you need to do to trigger a leak, then in another > window: su -s /bin/bash squid gdb squid > > At the gdb prompt: target remote | vgdb set logging file > /tmp/leaks.txt set logging on monitor leak_check full reachable > any > > This will dump out all the currently allocated memory to the > console (and to /tmp/leaks.txt). > Thanks. New patch added to bug 4088. Please see if it resolves the external_acl_type leak. Amos -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUNUSgAAoJELJo5wb/XPRjUTEH/A95Za6+QjzMwn2kSIkmHF2E FzEOPmC0t73lsHmVJptFnblsA2sKWgDokg+NRM1LISdLtx7EZ9aRN+8cQBBdCBnN AXuSz0nWUkI2ugPw6A5YOX70YEwwmkXiG52honyvmUsC0wyj5aBiAeNRZLfy5ZVo V1uSccJTeavrGPKgB5xrFVVEyF5oSMwxeM3Zu+lukgWKWHcIeSyFV2IJkvpG/Q/E U4JdLcWu3PjoZGQzHPIVGn0t+EaN9qVRDyq+p6E/weLvUhQqSi33qGJIoiZz7dbv 9zSEKegDv6+OGw4P8uEVzxebWSTCcr7NbYk/cUzMfg7fCp9zYed3MZL235O8JcM= =SlNr -----END PGP SIGNATURE----- _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
