Just to mention, I've already checked upstream. The port was working fine until some weeks ago. Now it doesn't even run and I can't find the culprit. The port compiles well (that's why there's a pkg available). I've tested with 13-RELEASE-p6, 13-RELEASE-p7 and 13-STABLE. Here's the gdb backtrace: Program received signal SIGSEGV, Segmentation fault. Invalid permissions for mapped object. 0x0000000802424a78 in vtable for __cxxabiv1::__si_class_type_info () from /lib/libcxxrt.so.1 (gdb) backtrace #0 0x0000000802424a78 in vtable for __cxxabiv1::__si_class_type_info () from /lib/libcxxrt.so.1 #1 0x00000008014629ea in __dynamic_cast () from /usr/local/lib/gcc10/libstdc++.so.6 #2 0x00000008014e8d36 in bool std::has_facet<std::ctype<char> >(std::locale const&) () from /usr/local/lib/gcc10/libstdc++.so.6 #3 0x00000008014daac5 in std::basic_ios<char, std::char_traits<char> >::_M_cache_locale(std::locale const&) () from /usr/local/lib/gcc10/libstdc++.so.6 #4 0x00000008014daf71 in std::basic_ios<char, std::char_traits<char> >::init(std::basic_streambuf<char, std::char_traits<char> >*) () from /usr/local/lib/gcc10/libstdc++.so.6 #5 0x000000080147707b in std::ios_base::Init::Init() () from /usr/local/lib/gcc10/libstdc++.so.6 #6 0x000000000043ab9e in ?? () #7 0x0000000800c45e8d in ?? () from /libexec/ld-elf.so.1 #8 0x00007fffffffe528 in ?? () #9 0x0000000000000011 in ?? () #10 0x0000000000000000 in ?? ()
Maintainer informed via mail
@Daniel If you are maintainer for this port, please update your Bugzilla email to match the current MAINTAINER line in the port. Could you also test a latest 12.x-RELEASE jail in poudriere. Are your tests for 13* using poudriere or a local system? I'd try to isolate and reproduce in poudriere. You may use the following `testport` arguments to enter the jail to run tests: -i -- Interactive mode. Enter jail for interactive testing and automatically cleanup when done. -I -- Advanced Interactive mode. Leaves jail running with port installed after test.
(In reply to Kubilay Kocak from comment #2) Yes, I'm aware of the email, I'm in process of changing the email to the right one, and since I'm moving, it'll take some time. I've tested with local and jail, I'll try with 12 to see what happens.
Compiling sdl_ttf2 without harfbuzz fixed the issue, as mentioned here: https://forums.freebsd.org/threads/openmsx-issue.84142/post-556512. Now my question is: How this can be fixed?
Created attachment 231842 [details] v1 Ok, I did some tests and now is working as expected. I've also created a pull request upstream: https://github.com/openMSX/openMSX/pull/1405 I've changed my mail to this new one (I will eventually do to other ports I have this week).
Upstream already fixed for the next version. The patch is still necessary for this version to work. Just to mention that openmsx without this fix is unusable on FreeBSD, so the package is broken.
Friendly ping. Is there something else needed here? The port remains unusable and the fix works well.
Created attachment 234553 [details] v2 Updated the patch since the maintainer mail was already changed.
18.0 was released and it fixes this issue, since upstream didn't cared enough for a software that actually doesn't work at all on ports.