Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just for a little clarification, when you say that it is crashing, is it locking the system up as well? In other words, are you having to reboot the system to recover from the crash?
Just for a little clarification, when you say that it is crashing, is it locking the system up as well? In other words, are you having to reboot the system to recover from the crash?
Let us know.
Just the application is freezing / crashing.. System is fine..
Just confused why coredump is not generated with all those settings...
doing a manual coredump via gdb command.. but not core dump automatically does not help when we are not monitoring.
This will attach strace to the process you give to the -p option. If you want to capture everything that happens when the program runs, you can use this:
Code:
~ $ strace -o <output_file.txt> -e trace=all <program executable> [<any args to the program>]
WARNING: Capturing everything can lead to VERY large trace output files!
And, lastly, to capture *just* the process management type calls (e.g. fork, wait, and exec), you can use the following:
Code:
~ $ strace -o <output_file.txt> -e trace=process <program executable> [<any args to the program>]
There are many options and ways to use strace to figure out where trouble may lie in the running of a given program, so definitely check man strace to use the other options if you don't find the core issue with my suggestions above.
HTH. Let us know.
Last edited by ShadowCat8; 04-04-2013 at 11:44 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.