Hide Forgot
Description of problem: Redhat has decided to make Linux harder to use. Version-Release number of selected component (if applicable): How reproducible: Use Redhat or Fedora to develop software. Discover that Fedhat goes out of it's way to make software development harder. Specifically: Write a program. Run the program. It crashes, with a "core dump" report. Search high and low for the core dump file. Discover that Redhat thinks that core dump files need to moved to directory to be sent upstream. Steps to Reproduce: 1. Assume that Redhat is a development platform. 2. 3. Actual results: Wasted time. Expected results: A powerful and efficient development platform. Additional info: I have been a RedHat user since '95 or so. As a professional software developer, it was the easily the best Linux distribution for me. Sadly, over the years, Redhat has become increasingly focused on data center users, providing features that have been correspondingly annoying for software developers. 'se_linux'? Disabled, as it automatically interferes with the software I'm writing. 'systemctl'? A buggy and overly complex solution to a problem I'm not experiencing. 'gnome'? As far as I can tell, it is an attempt to bring the Windows UI to Linux. If I thought that the Windows UI was a good idea, I would be using Windows, wouldn't I? And now I find that 'abrt' is actively making it harder for me to develop software. Goodbye, RedHat. I am moving over to BSD; you have plowed enough salt into Linux to drive me away. Goodbye. '
(In reply to charles.unix.pro from comment #0) > > And now I find that 'abrt' is actively making it harder for me to develop > software. We had to set MakeCompatCore option to "no" because systemd developers has decided to make RLIMIT_CORE = ulimited by default. If you want your programs to lay core files in CWD, set MakeCompatCore = yes in the /etc/abrt/plugins/CCpp.conf file and DefaultLimitCORE = 0 in the /etc/systemd/system.conf file. You can always remove abrt from your system (sudo dnf remove abrt\*).
I can see the value of centralized bug-reports, but it is sad that it is killing usability of the platform for developers. I had trouble getting reliably core-dumps from my own programs since F22 (or maybe even earlier). The problem just keeps on popping up every time again and again and again and ... Given your reply, I need to understand systemd, abrt, and probably abrt-cpp plugins and selinux at some point too, to get the "ulimit -c unlimited" honored. I tried it a few times, but I just get lost in technical discussions about issues that I completely fail to understand. Really, I don't want to know all the freaking details to report platform-provided binaries to somewhere, I only want to write and debug my own software on a reliable platform. Is Fedora so rarely used for development that it breaks regularly without any of you guys noticing it? abrt doesn't even mention how to get core-dumps for your own programs. There is no issue it seems for it not working, and clearly, it is not a critical property for a release or an update, or it would reliably work for me. Everybody seems focused on getting everything to some, to me, useless central point, and is completely forgetting normal developers that write code themselves on a reliable platform that just works.
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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.