[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dpdk-users
Subject:    Re: [dpdk-users] Segmentation fault in rte_eth_devices()
From:       Vincent Li <vincent.mc.li () gmail ! com>
Date:       2020-06-12 0:55:48
Message-ID: alpine.DEB.2.21.2006120046210.15256 () r220
[Download RAW message or body]



On Thu, 11 Jun 2020, David Aldrich wrote:

> Following on from my question, I want to enable more debug info in DPDK.  I
> am building DPDK using:
> 
> usertools/dpdk-setup.sh

When I use dpdk-setup.sh, after the first build, there is a target 
directory like x86_64-native-linuxapp-gcc created under dpdk root source 
directory, and there is '.config' file in x86_64-native-linuxapp-gcc 
directory, you can edit '.config' like 'CONFIG_RTE_LIBRTE_ETHDEV_DEBUG=y', 
then run dpdk-setup.sh again to build. this is one way to do it.

According to doc/build-sdk-quick.txt, you can also

make config T=x86_64-native-linuxapp-gcc

then manually edit x86_64-native-linuxapp-gcc/.config for your debug 
option


 > 
> Am I correct in thinking that the build commands in that script use make
> and I should modify the appropriate:
> 
> config/defconfig_*
> 
> file (defconfig_x86_64-native-linuxapp-gcc in my case) ?
> 
> If so, would these values be appropriate?
> 
> CONFIG_ RTE_LIBRTE_ETHDEV_DEBUG=y
> RTE_LOG_LEVEL=RTE_LOG_DEBUG
> RTE_LIBRTE_ETHDEV_DEBUG=y
> 
> (not sure whether all values should be prefixed by 'CONFIG_'?)
> 
> Finally, where do I specify '-O0 -g' for the DPDK build?

Again according to doc/build-sdk-quick.txt, maybe:

#EXTRA_CFLAGS='-O0 -g' make 



[prev in list] [next in list] [prev in thread] [next in thread]