I reran after implementing my app using GThreads and still got the
attached results after using: env G_DEBUG=gc-friendly
G_SLICE=always-malloc valgrind --leak-check=full --show-reachable=yes.
Notice also that there may be a small leak with g_thread_create(). Of
course this could also be how I'm
On 4/15/06, Nathaniel McCallum [EMAIL PROTECTED] wrote:
I hope this is the right list to ask this on. I ran valgrind on an
application I'm developing with glib using gmodule. Results attached.
I'm under the impression that valgrind and the new slice allocator
code do not really mix. There is
I hope this is the right list to ask this on. I ran valgrind on an
application I'm developing with glib using gmodule. Results attached.
Am I just worried about something that's not a big deal or is this a bug
I should file?
Thanks,
Nathaniel
==26126== ERROR SUMMARY: 0 errors from 0 contexts
