<div dir="ltr"><div>Hi Shailendra,<br></div><div><br></div><div>You may want to run your application using strace/ltrace which may help you identify which system call/library call is actually causing the crash. You may have to look around the application source surrounded by that system call/library call and have to find the clue. I am not aware of any other way to get the user level stacktrace.<br><br></div><div></div><div>Vishal<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 6, 2015 at 11:23 AM, Shailendra Rana <span dir="ltr"><<a href="mailto:shailendra.rana1982@gmail.com" target="_blank">shailendra.rana1982@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I have an application which traps file events using fanotify, process<br>
these events and gives a verdict to fanotify whether access to a file<br>
is allowed or not. However, in some cases the verdict does not reach<br>
fanotify and system freezes. In such a case I just have system crash<br>
to analyze the issue.<br>
<br>
My question is that is it possible to get a user level stack trace of<br>
an application using system crash ?<br>
<br>
Thanks and regards,<br>
Shailendra<br>
<br>
_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
</blockquote></div><br></div>