Re: Valgrind and DPDK - does it work ?

[Marc Sune <marc.sune-kpkqNMk1I7M@public.gmane.org>]

On 07/11/14 01:22, Marc Sune wrote:
> On 16/09/14 13:42, Morten Jagd Christensen wrote:
>> Hi all,
>>
>>
>> I am interested to hear if anyone here have had any luck running 
>> Valgrind on
>> DPDK applications?
>>
>>
>> I tried to use this some time ago, but Valgrind does not seem to work
>> together with hugepages – or
>>
>> I am doing something wrong ;-)
>>
>>
>> I would like to hear form anyone having success or failure with 
>> Valgrind and
>> DPDK.
>
> Found some time to have a close look. I also wanted to check a DPDK 
> app against valgrind. It works!
>
> I downloaded and compiled valgrind from sources (3.10.0) and applied 
> (manually) this patch:
>
> https://bugs.kde.org/attachment.cgi?id=85950&action=edit
>
> (Applied around line 2216)
>
> From this post:
>
> http://valgrind.10908.n7.nabble.com/mpich-unable-to-munmap-hugepages-td49150.html 
>
>
> Happy debugging
> Marc
>
Btw, I will debug closer my DPDK application, but a quick start and stop 
shows already some warnings:

==27534== Thread 2:
==27534== Syscall param epoll_ctl(event) points to uninitialised byte(s)
==27534==    at 0x65E6DBA: epoll_ctl (syscall-template.S:82)
==27534==    by 0x58DAEC: eal_intr_thread_main (in 
/home/marc/xdpd/build/src/xdpd/xdpd)
==27534==    by 0x5DD7B4F: start_thread (pthread_create.c:304)
==27534==    by 0x65E67BC: clone (clone.S:112)
==27534==  Address 0x7717d78 is on thread 2's stack
==27534==  in frame #1, created by eal_intr_thread_main (???)
==27534==

Regards
Marc