From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx.bisdn.de (mx.bisdn.de [185.27.182.31]) by dpdk.org (Postfix) with ESMTP id 790D77F18 for ; Fri, 7 Nov 2014 01:20:10 +0100 (CET) Received: from [192.168.1.43] (42.Red-79-146-253.dynamicIP.rima-tde.net [79.146.253.42]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.bisdn.de (Postfix) with ESMTPSA id 80D57A3956 for ; Fri, 7 Nov 2014 01:29:39 +0100 (CET) Message-ID: <545C1274.8020708@bisdn.de> Date: Fri, 07 Nov 2014 01:29:40 +0100 From: Marc Sune User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: dev@dpdk.org References: <007501cfd1a3$573fff00$05bffd00$@xenanetworks.com> <545C10D9.9020902@bisdn.de> In-Reply-To: <545C10D9.9020902@bisdn.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] Valgrind and DPDK - does it work ? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 00:20:10 -0000 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