Building main with Clang results in a segfault on launch
envgap__TwilitRealm__dusklight-2323
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
5f0f3d4ebe6a866b09ff4b304dd90ca9642b5a50- Manifest
CMakeLists.txt- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
TwilitRealm/dusklight #2323 · read the original issue
### Mods and Forks - [x] The bug occurs on an **official release** of Dusklight, without any forks or third-party patches installed ### Dusklight Version HEAD (5f0f3d4 ATTOW) ### Bug Description Using either the `linux-clang-debug` or `linux-clang-relwithdebinfo` build profiles to build Dusklight results in a `SEGV_MAPERR` when launching Dusklight. Seems to be related to **cxxopts** but I'm not entirely sure. Building with `linux-default-debug` or `linux-default-relwithdebinfo` works completely fine. ### Steps to Reproduce 1. Configure cmake with `linux-clang-debug` or `linux-clang-relwithdebinfo` 2. Build Dusklight with the same profile 3. Launch the Dusklight executable 4. See segfault ### Expected Behavior Dusklight doesn't segfault when launching after being built with Clang. ### Current Behavior Dusklight segfaults when launching after being built with Clang. ### OS / Architecture Linux x84-64 ### Game Disc GameCube PAL (Europe) ### Game Language English ### Graphics Backend Vulkan ### Texture Packs and Mods N/A - Dusklight doesn't even access the config folder before crashing. Can rename / remove `~/.local/share/TwiliRealm/Dusklight` and a new one isn't created. ### Logs and Other Files _No response_ ### Additional Context _No response_
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]