Re: [dpdk-dev] Using valgrind with DPDK app

[Stephen Hemminger <stephen@networkplumber.org>]

On Sat, 29 Aug 2020 19:54:08 +0200
Victor Huertas <vhuertas@gmail.com> wrote:

> Hello,
> 
> I have exactly the same problem as you. I have also downloaded, compiled
> and installed the very last version of valgrind (v3.17).
> As soon as the mempool is created, the program gets stuck.
> 
> If valgrind cannot be used with DPDK (I am using v18.11.5) as memory leak
> debugger, there must be other tool to do it. Which one?
> 
> Thanks for your attention
> 
> El vie., 10 jul. 2020 a las 16:59, Montorsi, Francesco (<
> fmontorsi@empirix.com>) escribió:  
> 
> > Hi all,
> > I would like to know if it's possible to run my DPDK application (I'm
> > using DPDK 19.11) under Valgrind.
> > I tried but it gets stuck apparently while accessing hugepages:
> >
> > ----
> > AL: Detected memory type: socket_id:0 hugepage_sz:1073741824
> > EAL: Detected memory type: socket_id:1 hugepage_sz:1073741824
> > EAL: Creating 4 segment lists: n_segs:32 socket_id:0 hugepage_sz:1073741824
> > EAL: Ask a virtual area of 0x1000 bytes
> > EAL: Virtual area found at 0x100033000 (size = 0x1000)
> > EAL: Memseg list allocated: 0x100000kB at socket 0
> > EAL: Ask a virtual area of 0x800000000 bytes
> > EAL: Virtual area found at 0x140000000 (size = 0x800000000)
> > EAL: Ask a virtual area of 0x1000 bytes
> > EAL: Virtual area found at 0x940000000 (size = 0x1000)
> > EAL: Memseg list allocated: 0x100000kB at socket 0
> > EAL: Ask a virtual area of 0x800000000 bytes
> > EAL: WARNING! Base virtual address hint (0xa80001000 != 0x1040000000) not
> > respected!
> > EAL:    This may cause issues with mapping memory into secondary processes
> > EAL: Virtual area found at 0x1040000000 (size = 0x800000000)
> > EAL: Ask a virtual area of 0x1000 bytes
> > EAL: Virtual area found at 0xac0001000 (size = 0x1000)
> > EAL: Memseg list allocated: 0x100000kB at socket 0
> > EAL: Ask a virtual area of 0x800000000 bytes
> > ----
> >
> > I've seen there was some attempt a few years ago:
> >     http://mails.dpdk.org/archives/dev/2016-February/033108.html
> > has anything changed since that?
> >
> > Also I see that Luca has created a project here
> >   https://github.com/bluca/valgrind-dpdk
> > but seems like there were no changes since 3 years... I wonder if that
> > works or not with recent DPDK versions...
> >
> > Thanks for any hint,
> >
> > Francesco Montorsi

Try the address-sanitizer option of Gcc or Clang. It works for applications.
I had issues with running on EAL startup.