-
-
Notifications
You must be signed in to change notification settings - Fork 844
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Crash]: Segmentation fault on dedicated server launch (Linux arm64) #12609
Comments
Relevant part of the crash:
|
I paid attention when running make this time and I saw these warnings: Long lines inside
Hope it's relevant to finding the solution to this |
I've compiled a 64-bit ARM build and I'm not seeing this issue. It is however the latest Pi OS, based on Debian 12.5 instead of 11. We switched to C++20 for OpenTTD 14, so maybe the c++ library or the compilers on Debian 11 is a bit old?
|
This can probably be closed with a mention of minimum compiler version in the COMPILING.md if that's the case |
Upgrade to debian 12 is complete, I ran Long lines inside
Despite this, the game succesfully compiled and runs with no apparent issues. |
Well it is in
|
Version of OpenTTD
14.0 Debian GNU/Linux 11 arm64
Steps to reproduce
I built release 14.0 on my raspberry pi 4b running Debian 11 arm64 just as I had previously done succesfully for version 13.4
This time there was this warning when running the cmake step (irrelevant lines omitted):
After that, running
make
produces an executable which, when ran, produces the attached crash files (no crash.dmp is produced due to a lack of breakpad)Steps followed:
release/14
branchcmake -DOPTION_DEDICATED=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
make
andmake install
/usr/local/games/openttd -D
Just to make sure that the warning was relevant, I checked out the
release/13
branch and ran the same cmake command, which produced no such errorOne last remark is that running
make test
produces the following two failed testsUpload crash files
crash.zip
The text was updated successfully, but these errors were encountered: