Sentry + custom native client + stack traces

I just struggled with this too, and couldn’t find a solution. It looks like Sentry lets you upload ELF debug info, but not on a per-release basis. Instead, it associates crashdumps with the correct version of the ELF file based on the “build ID” – which the docs falsely claims “all recent compilers add automatically” – but there’s no way to specify the build ID to use for a particular event. I guess this can only really be used for symbolicating crash dumps in some special format.

I could be wrong about all this, though. The docs aren’t very clear.

I ultimately ended up solving my problem by shelling out to addr2line to do symbolication before upload. This requires shipping the debug symbols along with the binary but I don’t have a problem with that for my use case.