DPDK usage discussions
 help / color / mirror / Atom feed
From: Vincent Li <vincent.mc.li@gmail.com>
To: David Aldrich <david.aldrich.ntml@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Segmentation fault in rte_eth_devices()
Date: Fri, 12 Jun 2020 00:55:48 +0000 (UTC)
Message-ID: <alpine.DEB.2.21.2006120046210.15256@r220> (raw)
In-Reply-To: <CAJK_ieiTn_0iNbs=OBQfmOfSYRrYsAmzMvFtDfvUQ+7X-ekULQ@mail.gmail.com>



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 




      reply	other threads:[~2020-06-12  0:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 16:28 David Aldrich
2020-06-11  8:57 ` David Aldrich
2020-06-12  0:55   ` Vincent Li [this message]

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=alpine.DEB.2.21.2006120046210.15256@r220 \
    --to=vincent.mc.li@gmail.com \
    --cc=david.aldrich.ntml@gmail.com \
    --cc=users@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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git