All of lore.kernel.org
 help / color / mirror / Atom feed
From: anupam.kapoor@gmail.com (Anupam Kapoor)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to get user level stack trace of an application from system crash
Date: Wed, 07 Oct 2015 15:39:00 +0530	[thread overview]
Message-ID: <87mvvv6ldv.fsf@fatcat.parallelwireless> (raw)
In-Reply-To: <CAOtxk7DWOZJ376ZMK_sqSt-4w4Ckta+BHOnWaXiwcF2OvdkAEg@mail.gmail.com>


>>>>> [2015-10-07T14:55:07+0530]: "Shailendra Rana" (shailendra.rana1982):
,----[ shailendra.rana1982 ]
| The application traps file events and send them over to other system
| via TCP. This other machine is running a third party solution which
| process these events and sends the verdict to the application which
| passes on the same to fanotify based on which decision of access to a
| file is made. I have seen this freeze issue in case of network
| failures but those are identifiable. There are couple of cases
| mentioned below which may lead to this.
| 
| 1) The event is received by third party solution but it did not send
| the verdict to the application. In that scenario need to notify this
| third party for fixing the issue.
| 2) Verdict is received by an application but could not pass on the
| same to fantiofy maybe it is stuck in an infinite loop. In this case I
| need to work towards fixing my application.
| 
| In order to identify the correct root cause I would want to have a
| user level stack trace of this application. Using crash tool I could
| not figure out the same.
| 
| I am using 3.13.0-24-generic #47-Ubuntu.
`----
one word: libunwind

also, this is not a kernel topic, afaik....
-- 
kind regards
anupam

      reply	other threads:[~2015-10-07 10:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06  5:53 How to get user level stack trace of an application from system crash Shailendra Rana
2015-10-07  6:50 ` Vishal Thanki
2015-10-07  9:30   ` Shailendra Rana
2015-10-07  8:40 ` Pranay Srivastava
2015-10-07  9:25   ` Shailendra Rana
2015-10-07 10:09     ` Anupam Kapoor [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=87mvvv6ldv.fsf@fatcat.parallelwireless \
    --to=anupam.kapoor@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.