Check build options
CONFIG_RTE_LIBRTE_MBUF_DEBUG
CONFIG_RTE_LIBRTE_MEMPOOL_DEBUG
and other CONFIG_RTE_*_DEBUG like flags
-----Original Message-----
From: SPDK [mailto:spdk-bounces@lists.01.org] On Behalf Of Naoki Iwakami
Sent: Friday, March 31, 2017 9:33 AM
To: spdk(a)lists.01.org
Subject: [SPDK] Access error and leak with rte_malloc'ed memory
Hello,
I am trying to find memory errors with memory blocks allocated by
rte_malloc in my SPDK application. Errors are such as buffer overrun,
memory leak, etc.
I found a Valgrind modified for DPDK. Thankfully, it works for SPDK, too.
https://github.com/bluca/valgrind-dpdk
But this tool seems not working for memory blocks allocated by rte_malloc.
As an alternative, does SPDK or DPDK have mechanism to support memory
error troubleshooting, such as putting magic words at memory
boundaries and giving current number of rte_malloc'ed bytes?
Regards,
--
Naoki Iwakami
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk