On 7 October 2015 at 12:20, Vishal Thanki <vishalthanki@xxxxxxxxx> wrote: > Hi Shailendra, > > 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. > > Vishal > > On Tue, Oct 6, 2015 at 11:23 AM, Shailendra Rana > <shailendra.rana1982@xxxxxxxxx> wrote: >> >> Hi, >> >> I have an application which traps file events using fanotify, process >> these events and gives a verdict to fanotify whether access to a file >> is allowed or not. However, in some cases the verdict does not reach >> fanotify and system freezes. In such a case I just have system crash >> to analyze the issue. >> >> My question is that is it possible to get a user level stack trace of >> an application using system crash ? >> >> Thanks and regards, >> Shailendra >> >> _______________________________________________ >> Kernelnewbies mailing list >> Kernelnewbies@xxxxxxxxxxxxxxxxx >> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > Hi, Yes, for in-house debugging it can be done but this may not be possible if this application is running on a customer system. In that case I would just have the crash dump. Thanks and regards, Shailendra _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
