In the last episode (Sep 29), Lefteris Tsintjelis said:
> Simon Barner wrote:
> >
> >Can you provide a (minimal) example where this happens? Also, what is
> >the exact command line?
>
> valgrind --trace-children=yes --leak-check=yes --show-reachable=yes ./sql-m
>
> ==12024== 200 bytes in 1 blocks are definitely lost in loss record 3 of 5
> ==12024== at 0x3C03619F: malloc (in
> /usr/local/lib/valgrind/vgpreload_memcheck.so)
> ==12024== by 0x3C0978EC: (within /usr/local/lib/valgrind/libpthread.so.1)
> ==12024== by 0x3C09A2FD: (within /usr/local/lib/valgrind/libpthread.so.1)
> ==12024== by 0x3C09A489: pthread_key_create (in
> /usr/local/lib/valgrind/libpthread.so.1)
It's probably leakage internal to valgrind, since the stack trace stops
inside a valgrind library. I wouldn't worry about it.
--
Dan Nelson
[EMAIL PROTECTED]
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
