From: Marc Sune <marc.sune@bisdn.de>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Valgrind and DPDK - does it work ?
Date: Fri, 07 Nov 2014 01:29:40 +0100 [thread overview]
Message-ID: <545C1274.8020708@bisdn.de> (raw)
In-Reply-To: <545C10D9.9020902@bisdn.de>
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
next prev parent reply other threads:[~2014-11-07 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 11:42 Morten Jagd Christensen
2014-11-07 0:22 ` Marc Sune
2014-11-07 0:29 ` Marc Sune [this message]
2014-11-07 1:04 ` Matthew Hall
2014-11-07 3:35 ` Marc Sune
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545C1274.8020708@bisdn.de \
--to=marc.sune@bisdn.de \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).