On Tue, 2020-08-04 at 21:36 +0200, Florian Weimer wrote: > * Jeff Law: > > > Actually, isn't it "just" 234MB. Still I'm surprised why that failed. Do we > > have more than one build running at a time on those boxes? > > It's a 32-bit build. I assume it's not the first large allocation. > (FWIW, GDB always prints “virtual memory exhausted”, even if the malloc > failure has a different cause.) > > Does LTO produce more complicated debugging information? Then maybe > disabling LTO on armhfp is a workaround. There's also a way to disable > debuginfo package generation altogether, something along these lines > (untested): It doesn't really make it more complicated, but it does scramble it in fun an interesting ways. I'd hazard a guess it changed things in such a way as to confuse the bits that add the index. Jeff > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
