I’m having an issue using the crashpad backend in our application. I’ve just updated our integration to the 0.1.4 native c++ sdk and during some tests when throwing exceptions at various places in the codebase I’m seeing the stacktrace in our sentry.io portal say that we are crashing in sentry_crashpad.dll in
HandleAbortSignal in crashpad_win_client.cpp line 188 instead of seeing a trace from where the crash actually took place.
When I don’t throw an exception but deference a nullptr or something else, I don’t have this problem and I see the correct stack trace at the correct location.
Is there something more than initializing the sentry SDK that i have to do to catch exceptions before reporting them to sentry? I was under the impression that crashpad would handle all that for me if i just initialized it?