* Miro Hrončok: > Hello, I've got this failure I cannot really understand, it happens on > armv7hl only (aarch64 and s390x were cancelled): > > Checking for unpackaged file(s): /usr/lib/rpm/check-files > /builddir/build/BUILDROOT/prusa-slicer-2.2.0-4.fc33.arm > error: Installed (but unpackaged) file(s) found: > /usr/bin/prusa-slicer.wrapped.gdb-index-9pY4kY > Installed (but unpackaged) file(s) found: > /usr/bin/prusa-slicer.wrapped.gdb-index-9pY4kY > > The gdb-index-9pY4kY files are not created explcitiyl by anything in > the package.
This happens if debuginfo generation fails with a crash: extracting debug info from /builddir/build/BUILDROOT/prusa-slicer-2.2.0-4.fc33.arm/usr/bin/prusa-slicer.wrapped ../../gdb/utils.c:691: internal-error: virtual memory exhausted: can't allocate 234696314 bytes. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] This is a bug, please report it. For instructions, see: <http://www.gnu.org/software/gdb/bugs/>. /usr/bin/gdb-add-index: line 106: 22699 Aborted (core dumped) $GDB --batch -nx -iex 'set auto-load no' -ex "file $file" -ex "save gdb-index $dwarf5 $dir" The crash is normally ignored. > Does anybody know what this is? Not enough RAM, apparently. Thanks, Florian _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
