mame package uses mame -validate as %check step. It has recently started
to cause problems on rawhide/aarch64:
- 0.259 build is stuck since ca. 1600 UTC yesterday [2]
I managed to reproduce this on the aarch64 machine in mock. Validation seems to get stuck right away at:
(gdb) bt
#0 0x0000aaaab5bddb08 in ___ZN4bgfx12VertexLayoutC1Ev_bti_veneer ()
#1 0x0000fffff5870b2c in __libc_start_main_impl () from /lib64/libc.so.6
#2 0x0000aaaaaef01570 in _start ()
One question: the binary in /builddir/build/BUILD still has symbols in, correct?
The backtrace above does not contain a filename or line number for frame #0,
so it looks like the app (or a library that it uses) was compiled without "-g",
or the debug information has been stripped or separated after building.
Of course the app does contain some global symbol information
that is required for run-time dynamic linking ("readelf --symbols
--use-dynamic ./my_app"). It is remarkable that the symbol
for frame #0 '___ZN4bgfx12VertexLayoutC1Ev_bti_veneer'
begins with three underscores instead of only 1.
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
