top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

When Linux Crashes, Where will be the dump file?

+1 vote
477 views

I want to see why my linux system got crashed,
Can anyone please tell where will be the dump file/ How to debug it?

posted Jul 13, 2016 by Chirag Gangdev

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

1 Answer

+1 vote
 
Best answer

The default crash directory is /var/crash. You can change the path to anything you want, provided there's enough space on the target device.

You can change this path either using GUI tools or manually editing the Kdump configuration file:
/etc/sysconfig/kdump on openSUSE
/etc/kdump.conf on CentOS (RedHat)

answer Jul 13, 2016 by Salil Agrawal
Similar Questions
+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
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.

+3 votes
In linux, process running in background will be killed if we close the terminal?

Please understand the scenario :

I have an embedded system, on which i do telnet and then i starts i run an application using ./binary_name &.
Now if i close the terminal, and if i do telnet from new terminal then i can see above process is still running.

Now, To check this, i have written a sample program,

#include<stdio.h>
main()
{
    while(1);
}

I just compiled it and i ran it on my linux PC using ./a.out &.
Then i just closed the terminal and from new terminal i checked using ps -elf command this process was killed.

My question is why different behavior for both process. i started both the process in background. Then why?

Any suggestion?

Thanks in advance

...