Description of problem: on occasion, a build will fail due to a segfault by gcc or other such apps. It would be beneficial to capture the core files produced in such failures to include in the resultdir, to help determine the source of the underlying failure. While such failures cause a FTBFS, the root cause bug is going to be in the compiler.
-- Any proposal for how to do this? -- Any reason this could not be done by a separate program?
Adding FutureFeature keyword to RFE's.
(In reply to comment #1) Just some thoughts off the cuff, not sure about doability/feasibility: > -- Any proposal for how to do this? If a build fails, find filenames matching "core(\.\d+)?" from build root, copy them somewhere below resultdir along with their relative parent dirs from build root (cp --parents). BTW, config.log (autoconf log) would be nice to have similarly stashed in resultdir if it's found in build dir. Perhaps also logs for other common build tools (cmake, scons?) if they have predictable file names. Maybe stash all these even if the build succeeds, and output a warning if core files were found? > -- Any reason this could not be done by a separate program? I suppose that wouldn't work with the tmpfs plugin.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
How would you feel about it being a plugin? I figure we could install a 'postbuild' hook that would scan the chroot for files of interest and then copy them into the result dir. Would that work for you?
Created attachment 734384 [details] initial cut at chroot_scan plugin Here's my first try at a plugin that when enabled will scan the chroot for files matching the regex'es passed in. Please let me know if this is close to what you want.
mock-1.1.31-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mock-1.1.31-1.fc19
mock-1.1.31-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mock-1.1.31-1.fc17
mock-1.1.31-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.31-1.el6
mock-1.1.31-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mock-1.1.31-1.fc18
Package mock-1.1.31-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mock-1.1.31-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5858/mock-1.1.31-1.fc19 then log in and leave karma (feedback).
mock-1.1.32-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mock-1.1.32-1.fc17
mock-1.1.32-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mock-1.1.32-1.fc18
mock-1.1.32-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.32-1.el6
mock-1.1.32-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mock-1.1.32-1.fc19
mock-1.1.32-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.32-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.32-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.