On 09/03/2013 05:27 PM, Ronald Moesbergen wrote: > Is there anything I can do to help > debug this? I'm running on Ubuntu 12.04, version 3.1.4, gmime 2.6.7-1.
I use: G_SLICE=all valgrind \ --leak-check=full \ --suppressions=contrib/dbmail.supp --log-file=/tmp/vg.log src/dbmail-imapd -D keep it running while you run your tests. When done, stop valgrind, and save /tmp/vg.log somewhere. The suppressions file is in the source-tree. Don't use jemalloc when you do this. I also assume you didn't activate the memory pool system by setting DM_POOL=yes in the environment. G_SLICE=all will make sure glib doesn't use the internal slice allocator since valgrind doesn't know how to debug that one. If this doesn't reveal any leaks, there _may_ still be leakage in the GObject system. Following can be used to track that: git://git.subdir.eu/paul/gobject-list which is a fork of http://cgit.collabora.com/git/user/danni/gobject-list.git it helped a *lot*. -- ________________________________________________________________ Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin * Premium Hosting Services and Web Application Consultancy * www.nfg.nl/[email protected]/+31.85.877.99.97 ________________________________________________________________ _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
