Bug 1460572 - core dump not generated in fedora 25
core dump not generated in fedora 25
Status: NEW
Product: Fedora
Classification: Fedora
Component: systemd (Show other bugs)
x86_64 Linux
unspecified Severity urgent
: ---
: ---
Assigned To: systemd-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-06-12 01:02 EDT by n_jayshankar
Modified: 2017-11-16 14:02 EST (History)
17 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description n_jayshankar 2017-06-12 01:02:47 EDT
Description of problem:
I have written a snippet of code to generate core dump.
File: a.c

#include <stdio.h>
char **c;

gcc a.c -o a -g

In fedora 25 after segmentation fault, core dump  file is not being created. 

I have also set the core file to unlimit with the command ulimit -c unlimited.
Comment 1 Kamil Dudka 2017-06-12 10:09:03 EDT
Please check the contents of /proc/sys/kernel/core_pattern.  As far as I know, f25 uses systemd-coredump by default.  The core dumps are then available via coredumpctl(1).

Note that you can use gdb(1) to create core dumps manually anytime anywhere.
Comment 2 Fedora End Of Life 2017-11-16 14:02:56 EST
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Note You need to log in before you can comment on or make changes to this bug.