[lttng-dev] Valgrind Memory Error in lttng-relayd

Aravind HT aravind.ht at gmail.com
Thu Jul 2 12:42:13 EDT 2015


Possible Solution :

The following changes seem to be missing from the actual code

http://git.lttng.org/?p=lttng-tools.git;a=commitdiff;h=cd2ef1ef1d54ced9e4d0d03b865bb7fc6a905f80


only the connection.h changes have been absorbed, while the main.c changes
left out.

On Mon, Jun 29, 2015 at 11:51 PM, Aravind HT <aravind.ht at gmail.com> wrote:

> Hi,
>
> I ran valgrind on lttng-relayd for a soft hang issue that I had reported
> earlier.
> http://lists.lttng.org/pipermail/lttng-dev/2015-May/024533.html
>
> Below are the list of errors that I found.
>
> ==793== Thread 4:
> ==793== Invalid write of size 8
> ==793==    at 0x406038: cds_list_add (list.h:53)
> ==793==    by 0x409442: queue_stream (main.c:1175)
> ==793==    by 0x409AB7: relay_add_stream (main.c:1274)
> ==793==    by 0x40C47A: relay_process_control (main.c:2099)
> ==793==    by 0x40DBB1: relay_thread_worker (main.c:2574)
> ==793==    by 0x5BDAFE2: start_thread (pthread_create.c:312)
> ==793==    by 0x5ED8AFC: clone (clone.S:111)
> ==793==  Address 0x6e09040 is 64 bytes inside a block of size 312 free'd
> ==793==    at 0x4C2898C: free (in
> /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==793==    by 0x418EF8: rcu_destroy_stream (stream.c:33)
> ==793==    by 0x5079C94: ??? (in /usr/lib64/liburcu.so.2.0.0)
> ==793==    by 0x5BDAFE2: start_thread (pthread_create.c:312)
> ==793==    by 0x5ED8AFC: clone (clone.S:111)
> ==793==
>
> Are there any known bugs/fixes for these ?
>
>
> Regards,
> Aravind.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150702/8e03ab79/attachment.html>


More information about the lttng-dev mailing list