Re: Disabling ABRT?
On 12/28/2013 10:48 PM, Richard Fearn wrote: Hi, On 28 December 2013 21:29, Brendan Jones brendan.jones...@gmail.com wrote: I'm doing some development at the moment and I want the coredumps to be dropped somewhere sane (like the executing directory). How do I do it? I think you want to do: $ sudo systemctl stop abrt-ccpp Before: $ cat /proc/sys/kernel/core_pattern |/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e i.e. send core dumps to abrt. After: $ cat /proc/sys/kernel/core_pattern core $ cat /proc/sys/kernel/core_uses_pid 1 i.e. write core dumps to files named core.xxx. Regards, Rich Thanks. I had tried this but still no core in the executing directory. Now I'm not sure where they are going - certainly nowhere in $HOME. Its a difficult program to debug (an audio plugin kicked off by a host program) but I seem to have fixed the problem so it's no longer gracelessly crashing. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Disabling ABRT?
On 29 December 2013 11:29, Brendan Jones brendan.jones...@gmail.com wrote: Thanks. I had tried this but still no core in the executing directory. Now I'm not sure where they are going - certainly nowhere in $HOME. Could be a couple of things: 1. The core dump limit for the process could be 0 (i.e. don't write core dumps). 2. The core dumps are written to the cwd of the process at the point where it dies - not necessarily where you run it from. (If you know the PID you could check /proc/pid/cwd.) Rich -- Richard Fearn richardfe...@gmail.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Disabling ABRT?
On Sun, 29 Dec 2013 13:17:49 +0100, Richard Fearn wrote: On 29 December 2013 11:29, Brendan Jones brendan.jones...@gmail.com wrote: Thanks. I had tried this but still no core in the executing directory. Now I'm not sure where they are going - certainly nowhere in $HOME. Could be a couple of things: 1. The core dump limit for the process could be 0 (i.e. don't write core dumps). 2. The core dumps are written to the cwd of the process at the point where it dies - not necessarily where you run it from. (If you know the PID you could check /proc/pid/cwd.) That is ABRT running/not-running should not have any effect on the normal 'ulimit -c' behavior. It was filed for ABRT and fixed in 2009: https://bugzilla.redhat.com/show_bug.cgi?id=530637 If stopping/starting ABRT changes anything - that is ABRT behavior is not fully transparent - it is a new ABRT bug. Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Disabling ABRT?
On 12/29/2013 05:37 PM, Jan Kratochvil wrote: On Sun, 29 Dec 2013 13:17:49 +0100, Richard Fearn wrote: On 29 December 2013 11:29, Brendan Jones brendan.jones...@gmail.com wrote: Thanks. I had tried this but still no core in the executing directory. Now I'm not sure where they are going - certainly nowhere in $HOME. Could be a couple of things: 1. The core dump limit for the process could be 0 (i.e. don't write core dumps). 2. The core dumps are written to the cwd of the process at the point where it dies - not necessarily where you run it from. (If you know the PID you could check /proc/pid/cwd.) That is ABRT running/not-running should not have any effect on the normal 'ulimit -c' behavior. It was filed for ABRT and fixed in 2009: https://bugzilla.redhat.com/show_bug.cgi?id=530637 If stopping/starting ABRT changes anything - that is ABRT behavior is not fully transparent - it is a new ABRT bug. Jan Yup. Thanks guys. ulimit -c was 0 ulimit -c unlimited Fixes my problem. Cores created in the cwd. I would have thought that this should be enabled by default in /etc/security/limits.conf in the absence of abrt. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Disabling ABRT?
On Sat, 2013-12-28 at 20:17 -0600, Michael Catanzaro wrote: For unpackaged executables, ABRT should be creating core dumps in the processes' directory, so you shouldn't need to disable it. I think that might be broken, though. For the record, since I suggested this might be broken: it's broken whenever I forget to use ulimit -c, and not broken otherwise. :) signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Disabling ABRT?
Hi, On 28 December 2013 21:29, Brendan Jones brendan.jones...@gmail.com wrote: I'm doing some development at the moment and I want the coredumps to be dropped somewhere sane (like the executing directory). How do I do it? I think you want to do: $ sudo systemctl stop abrt-ccpp Before: $ cat /proc/sys/kernel/core_pattern |/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e i.e. send core dumps to abrt. After: $ cat /proc/sys/kernel/core_pattern core $ cat /proc/sys/kernel/core_uses_pid 1 i.e. write core dumps to files named core.xxx. Regards, Rich -- Richard Fearn richardfe...@gmail.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Disabling ABRT?
On Sat, 2013-12-28 at 21:48 +, Richard Fearn wrote: Hi, On 28 December 2013 21:29, Brendan Jones brendan.jones...@gmail.com wrote: I'm doing some development at the moment and I want the coredumps to be dropped somewhere sane (like the executing directory). How do I do it? I think you want to do: $ sudo systemctl stop abrt-ccpp You should use 'systemctl disable' instead of 'systemctl stop' if you want the change to be persistent across reboots. For unpackaged executables, ABRT should be creating core dumps in the processes' directory, so you shouldn't need to disable it. I think that might be broken, though. signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
