Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
ulimit -c can be used to set RLIMIT_CORE, and limit the maximum size of a coredump a process may generate. Any larger coredump will be truncated to this size.
Can anything useful be done with such a truncated coredump? Perhaps on a platform other than Linux x86-64, or with a debugger other than GDB?
If not, why does POSIX specify this behavior, rather than, say, truncating a coredump to zero bytes if RLIMIT_CORE is exceeded?
Yes, lots of things.
The truncated core dump will usually contain the stack segments, so the commands
whereandthread apply all wherewill usually work. Often that’s all one needs from a core. Commands to examine local variables and globals will likely work as well.Commands to examine heap-allocated variables may work for some variables, but not necessarily for others. Still, this is much better than nothing.