On Thu, Sep 15, 2016 at 8:17 AM, Michael Catanzaro <mcatanzaro@xxxxxxxxx> wrote: > Hi, > > Something between F23 and F24 broke coredumpctl in Fedora. It's still > broken. Appears to be an SELinux bug. It's reported as [1]. I want > coredumpctl to be enabled by default in F26 as a F26 feature, but I can > hardly go ahead and propose that while it's still broken. It would be > great if the SELinux developers could look into the issue. systemd > developers have been responsive and already left several comments in > the bug, but I've failed to get the attention of SELinux folks thus > far. I think that's only part of the problem. I regularly get: is not a core dump: File format not recognized I asked about it on systemd list and there's no reply. And very often now I get this: More than one entry matches, ignoring rest. I get that message whether I specify by PID or by EXE. The man page example by path to executable says it'll dump the most recent core file, but it doesn't. I get the 'more than one entry matches' and it creates a 0 length file. I have entries going back to June, inevitably there are duplicates. There's also no command to clean things up. And my favorite: Refusing to dump core to tty. OK fine, so lets use --output= and dump it to a file! Cannot retrieve coredump from journal nor disk. Coredump retrieval failed: No such file or directory OK so it exists, but can't go to tty... oh wait you want it output to a file? No it doesn't exist. What? -- Chris Murphy -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
