[HanziQ][16.0][macOS 10] Crash on start: EXC_CRASH (SIGABRT); DYLD, [0x4] Symbol missing
Re: [HanziQ][16.0][macOS 10] Crash on start: EXC_CRASH (SIGABRT); DYLD, [0x4] Symbol missing
I want to try one last thing before giving up on 10.9
Re: [HanziQ][16.0][macOS 10] Crash on start: EXC_CRASH (SIGABRT); DYLD, [0x4] Symbol missing
@SupplyDepoo: can you post also crash log from 0.16.16 when attempting to load a save, please? The one you posted is from creating new map, and I found out loading save doesn't call same function that causes crash on creating new map.
- SupplyDepoo
- Filter Inserter
- Posts: 305
- Joined: Sat Oct 29, 2016 8:42 pm
- Contact:
Re: [HanziQ][16.0][macOS 10] Crash on start: EXC_CRASH (SIGABRT); DYLD, [0x4] Symbol missing
So we changed file copying routines to not use standard C++ copy_file function on OS X 10.9, and instead use mac specific copyfile()
Can you try 0.16.22, please?
Can you try 0.16.22, please?
- SupplyDepoo
- Filter Inserter
- Posts: 305
- Joined: Sat Oct 29, 2016 8:42 pm
- Contact:
Re: [HanziQ][16.0][macOS 10] Crash on start: EXC_CRASH (SIGABRT); DYLD, [0x4] Symbol missing
Great! I'm cancelling all of my plans for this week.
It works!!!!! Thank you so much!
⚙ BEST DEVS EVER! ⚙
It works!!!!! Thank you so much!
⚙ BEST DEVS EVER! ⚙
Re: [HanziQ][16.0][macOS 10] Crash on start: EXC_CRASH (SIGABRT); DYLD, [0x4] Symbol missing
Yay! Thanks for your cooperation on this
Re: [HanziQ][16.0][macOS 10] Crash on start: EXC_CRASH (SIGABRT); DYLD, [0x4] Symbol missing
Hooray, it's working! Thank you so much for not giving up on us!
-
- Manual Inserter
- Posts: 4
- Joined: Sat Feb 03, 2018 1:49 am
- Contact:
Re: [HanziQ][16.0][macOS 10] Crash on start: EXC_CRASH (SIGABRT); DYLD, [0x4] Symbol missing
hi, just noticed this now after reading in the friday facts. wish i saw it earlier.
reasoning behind this problems:
the c++ stl libary is included in the OS for macOS, (and linked dynamically). if you use a newer c++ standard than the lib provided in the OS such problems appear.
in this case the c++17 filesystem was used (propably replaced the boost one)
possible solutions:
- drop some older macOS versions
- only use new language features, but avoid the library features
- have a wrapper for these and use boost (or other implementation) for support of older os versions (most stl and boost stuff is quite similar, allowing for a simple wrapper)
be aware of following c++17 features that may cause similar problems when used:
std::variant
std::optional
std::any
std::string_view
std::invoke
std::apply
std::filesystem
std::byte
+ some new map insertion methods (try_emplace and insert_or_assign)
reasoning behind this problems:
the c++ stl libary is included in the OS for macOS, (and linked dynamically). if you use a newer c++ standard than the lib provided in the OS such problems appear.
in this case the c++17 filesystem was used (propably replaced the boost one)
possible solutions:
- drop some older macOS versions
- only use new language features, but avoid the library features
- have a wrapper for these and use boost (or other implementation) for support of older os versions (most stl and boost stuff is quite similar, allowing for a simple wrapper)
be aware of following c++17 features that may cause similar problems when used:
std::variant
std::optional
std::any
std::string_view
std::invoke
std::apply
std::filesystem
std::byte
+ some new map insertion methods (try_emplace and insert_or_assign)