top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

What are the debuging information in core file ?

+4 votes
447 views

What are the information we can find from core file?

posted Nov 8, 2013 by Anuj Yadav

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

At the minimal, you would find the local variables, global variables and stack trace (of multiple threads too, if the the program was multi-threaded).

However, it is possible that the very reason for crash is stack corruption, and in that case, stack trace would be tricky.

Also, most released code binaries are stripped - so you won't see the exact function names in stack trace. You would have to point to appropriate symbols to see proper function names.

answer Feb 22, 2014 by Mehul Bhatt
Similar Questions
+2 votes
How to save the core file to disk?

My program Seg faults but cannot find where Ubuntu saves the core file.

I have changed the core_pattern as follows but still no core file:
echo "core.%e.%p" > /proc/sys/kernel/core_pattern

I want to debug and see where it is crashing. Appreciate if someone could help to generate the core file disk.

+1 vote
While debugging CORE file with GDB, Why we have to use executable file also along with that?

As far as I know, CORE file contains all the information till Segmentation fault. Then, while debugging core file why we are using executable file(binary) with it.?

+2 votes
Core file location and abrt in Linux(fedora)

I'd like to ensure core files go to a local partition rather than the default location ($HOME), which is network-mounted in my case.

Googling a bit, I found this: https://access.redhat.com/site/solutions/61536

In light of that, a few questions... Does this still apply to abrt in Fedora 19?

That page suggests that when abrt is in use, core files would be generated in the location set by abrt, which defaults to /var/spool/abrt. However, I have abrtd running and I'm definitely getting core files in $HOME. Does abrt just make a copy to put in /var/spool/abrt?

Might my problem be resolved as simply as telling abrt not to make a copy? I'd be fine with just having the core files in /var/spool/abrt. Otherwise, I imagine I'd like them somewhere named /var/users/$USER/dump
(or similar). How do I do that and continue to play nicely with abrt?

+2 votes
GDB: What is the interpretation of "info signals" information shows in gdb ?

There is a huge list shown by command "info signals" with the GDB.
Can someone please explain about these information in details ?
How can an user interpret these information ?

...