DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Shankari Vaidyalingam <shankari.v2k6@gmail.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Debug info
Date: Mon, 20 Apr 2015 18:04:16 +0000	[thread overview]
Message-ID: <D15AA8E6.1D77A%keith.wiles@intel.com> (raw)
In-Reply-To: <CAGeyXNdFhGXYYVtkcm3Ut0AonrBScxUY-69+fWd7ttSGz5FybQ@mail.gmail.com>



On 4/20/15, 12:51 PM, "Shankari Vaidyalingam" <shankari.v2k6@gmail.com>
wrote:

>Hi,
>
>I have developed an application with DPDK.
>While executing the same I can see the application quitting half way (i.e
>producing only half of the expected output - terminating abruptly).
>I think that something is going wrong which is causing the program to
>crash.
>
>Would like to know if it is possible to get the crashdump with programs
>written in DPDK.
>If possible please let me know how I can use GDB to debug the crash.
>I have heard that rte_panic is used for creating stack trace. As per my
>understanding I think that can be done if I know the exact statement which
>is causing the crash. But in my application I'm not able to trace the
>exact
>location of failure as the output differs during each run.

I use gdb and cgdb to debug pktgen application on Ubuntu 14.04

sudo cgdb ./app/pktgen

Then
gdb> run -c 1f -n 2 Š

This works very well, but you need to make sure you compile DPDK and your
application with option -g or -g -O0

Using Œmake install T=x86_64-native-linuxapp-xclang¹ EXTRA_CFLAGS+=³-g
-O0"' 
>
>Pls help.
>
>Regards
>Shankari.V

      reply	other threads:[~2015-04-20 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 17:51 Shankari Vaidyalingam
2015-04-20 18:04 ` Wiles, Keith [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=D15AA8E6.1D77A%keith.wiles@intel.com \
    --to=keith.wiles@intel.com \
    --cc=dev@dpdk.org \
    --cc=shankari.v2k6@gmail.com \
    /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).