DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shankari Vaidyalingam <shankari.v2k6@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Debug info
Date: Mon, 20 Apr 2015 23:21:07 +0530	[thread overview]
Message-ID: <CAGeyXNdFhGXYYVtkcm3Ut0AonrBScxUY-69+fWd7ttSGz5FybQ@mail.gmail.com> (raw)

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.

Pls help.

Regards
Shankari.V

             reply	other threads:[~2015-04-20 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 17:51 Shankari Vaidyalingam [this message]
2015-04-20 18:04 ` Wiles, Keith

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=CAGeyXNdFhGXYYVtkcm3Ut0AonrBScxUY-69+fWd7ttSGz5FybQ@mail.gmail.com \
    --to=shankari.v2k6@gmail.com \
    --cc=dev@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
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).