terminating with uncaught exception of type std::bad_cast: std::bad_cast
I'm trying to run a Satisfactory dedicated server on ARM64 (4 cores 24gb of RAM). I'm using box64 and box86 to boot the server. Whenever I do, it crashes with this error message: " terminating with uncaught exception of type std::bad_cast: std::bad_cast". I was told to put this here, sorry if it's in the wrong spot.
That's fine, you are in the right place (I asked you to create the ticket here :) )
How did you install that Satisfactory server? using steamcmd or something else?
I installed it with steamcmd running on box86, then ran it using box64. I'm on ubuntu. Full error is:
terminating with uncaught exception of type std::bad_cast: std::bad_cast Signal 6 caught. Malloc Size=65538 LargeMemoryPoolOffset=65554 CommonUnixCrashHandler: Signal=6 Segmentation fault (core dumped)
FWIW, I'm running into the same issue
I am also having this issue, hope my logs can provice help to wy it doesn't work and how this can be fixt
https://hastebin.com/izisilonax.md
https://hastebin.com/bojajowuki.md
I'm trying to pull the same stunt, and I'm dealing with the same error.
For reproduction:
- Create a free server on Oracle Cloud (4 Ampere aarch64 cores + 24GB, Ubuntu Canonical)
- Install box64 and box86 using the custom repos
- Move the Satisfactory Dedicated Server to the server (I couldn't get SteamCMD to run, but it's not required)
- Run (I use
BOX86_NOBANNER=1 ./FactoryServer.shjust in case)
My output looks very similar to the second hastebin posted by Quinten above. I believe the actual error occurs on logline 521.
Let me know if there's anything I can do to help and thank you for your hard work!
some documentiation I found arround this error
- https://en.cppreference.com/w/cpp/types/bad_cast
- https://stackoverflow.com/questions/19960496/compiles-but-getting-uncaught-exception-of-type-stdbad-cast
Same error, following this guide to setup an environment: https://github.com/Raezroth/Linux-ARM-Gaming-Chroot/blob/master/README.md . Then installed SteamCMD, downloaded the game and started in the chroot env. Crashing with
terminating with uncaught exception of type std::bad_cast: std::bad_cast
Signal 6 caught.
Malloc Size=65538 LargeMemoryPoolOffset=65554
CommonUnixCrashHandler: Signal=6
[2022.11.20-14.55.58:525][ 0]LogCore: === Critical error: ===
Unhandled Exception: SIGABRT: abort() called
[2022.11.20-14.55.58:526][ 0]LogCore: Fatal error!
0x0000ffff87d87642 libUE4Server-Core-Linux-Shipping.so!FUnixPlatformStackWalk::CaptureStackBackTrace(unsigned long long*, unsigned int, void*) [D:/ws/SB-220602145101-842/UE4/Engine/So
urce/Runtime/Core/Private/Unix/UnixPlatformStackWalk.cpp:693]
[2022.11.20-14.55.58:538][ 0]LogExit: Executing StaticShutdownAfterError
Any updates on this? I basically want to do the same.
Is it still happening?
Is it still happening?
yes it is
Mmmm, ok. I'll install Satisfactory on my arm test machine and will give a it try
note for my that is I am trying to run the server not the game itself
Yeah ok. There is a separate download on steam for the Dedicated server, so I'll use this
So, I did try and indeed I get Segfault. After some analysis, t's a cycling lib dependancly: A use B, and B use A. Not sure how I will handle that.
How did you identify this? Just out of curiosity. I am not a C expert
That's not the whole story. (I found at using gdb, it was obvious there).
Once I workaround this recursive lib stuff, I actually get the std::bad_cast: std::bad_cast message. So, I need to check what's wrong there too.
Any updates ?
I did some debugging, but didn't found anything conclusive. I'm still unsurre why it happens, I need to speed more time on this.
Is there any possible way how we could help ?
Not sure. The exception occurs during the initialisation of lib. I really haven't found enough detail yet. I suspect it's an issue with the elfloader / librarian, with somehow an issue with a wrong symbol being used. But I really need to put more time in this to really get the symbol being executed that launch the exception. It's a dynamic value, not a static one, so I need to analyse (unless someone with debugging knowledge and good understanding of the ELF structure and runtime linking want to take over)
No updates right ?