pthom
commented
4 months ago Hello!
The crash originates from an abort() call within HelloImGui::LoadAssetFileData(char const*)
The log should display the name of the file that is not found. If it does not display the name of the file, there might be another source of the error.
Interesting point: files are copied at CMake configure step. If a file is not found, you might want to run CMake another time.
an ".app" is simply a "package" folder whose content is hidden by default:
And here is an example content of such a package: In the image below, the executable is "Contents/MacOS/demo_docking"
It is perfectly possible to attach a debugger to an app contained in such a package.
When using CMake, you can also pass -DHELLOIMGUI_MACOS_NO_BUNDLE=ON to force the creation of standard binaries.
starlight-traveler
Hello!
I attempted to build the bundle to see how hard it would to integrate into a long standing cmake project, and it seems that the .app that gets created calls abort(). I could not figure out to just output a bin file to attach a debugger, but the Darwin stderr references such:
The crash originates from an abort() call within HelloImGui::LoadAssetFileData(char const*). Problem related to asset loading, possibly because a file could not be found or accessed correctly.
Specifically, HelloImGui::LoadFontTTF. This is likely due to an attempt to load a font file that cannot be found or read, however I do not know which one or where in the code and several calls it references?
Is there
1) A way to just output a bin file instead of an app to attach a debugger?
2) Where would I start finding the asset error if I can not use a debugger?