iOS call stack support

[arizigler]

Hi,

First and foremost - I find this tool amazing! Thank you so much for putting effort into it!

I Was trying to use tracy with a library I wrote in c++ in iOS environment.

It all seemed to work great except for missing call stacks.
In #8 I saw that you mentioned that it makes no sense to catch crashes on iOS as there are no symbols on the device.

I don't know about crashes (as I didn't test it yet) but for typical profiling I managed to workaround this issue by:

1. removing the ".app" suffix from the dSYM file (currently its auto-generated name is .app.dSYM) due to macho.cpp's search path expectation (dsymsuffixdir).
2. pushing the dSYM file alongside my app's binary (as I do for any other resource needed during runtime).

I've decided to share my findings here for my fellas iOS programmers and for you to consider adding these as side notes to the manual.

Tnx.

[wolfpld]

That's a great find! But can you provide a more detailed description? For example, what is your build environment, are you using Xcode, or some sort of custom makefiles? Where can you find the dSYM file? How can it be pushed to the target device? Can this process be automated, so that Xcode builds do this automatically?

[wolfpld]

Also tagging @thedmd, I'm sure he will be interested.

[arizigler]

@wolfpld, sure.
I'm using XCode 11.4.1 and integrated the process into its Build-Phase by adding a "New Run Script Phase":

It's worth mentioning, though, that in order to fire up the static profiler's constructor I had to add the following lines of code in the global area:

auto const& profiler = tracy::GetProfiler();

I've verified that the above call is executed before the ObjC "main" function, as intended.

---- edit:
The copy line in the script shall be:
cp -rf ${TARGET_BUILD_DIR}/${WRAPPER_NAME}.dSYM/ ${TARGET_BUILD_DIR}/${UNLOCALIZED_RESOURCES_FOLDER_PATH}/${PRODUCT_NAME}.dSYM
(note the asterisk (*))