Sentry-native catch exception stacktrace
Description
When capturing an exception with sentry-native, it claims that it is unable to find the debug info file of my executable with debug id 0000000-0000-0000-0000-000000000
2 things;
-
i have uploaded my debug info files and when an exception is 'auto-captured'
via throw exception and not with sentry, it manages to find the correct debug info file with the right debug id and shows its stacktrace. -
my debug info file debug id is not 0000000-0000-0000-0000-000000000, and it seems like when manually capturing the exception and creating a new stacktrace as shown in code, it generates a debug id full of 0s instead of the correct one.
i compared the event payload json file, and for the event of capturing an exception that generates the debug id of 0s, there is no code_id in debug_meta info, while code_id exists when exception is 'auto-captured'.
When does the problem happen
- [] During build
- [] During run-time
- [x] When capturing a hard crash
Environment
- OS: Linux
- Compiler: [e.g. MSVC 19]
- CMake version and config: 3.18.4, SENTRY_BACKEND=(i am not sure)]
Steps To Reproduce
sentry_value_t exc = sentry_value_new_exception("dummyexception, "dummy");
sentry_value_t stacktrace = sentry_value_new_stacktrace(NULL, 0);
sentry_value_set_by_key(exc, "stacktrace", stacktrace);
sentry_value_t event = sentry_value_new_event();
sentry_event_add_exception(event, exc);
sentry_capture_event(event);
Log output
You noted that you are on Linux, and manually capturing an event via sentry_capture_event.
By "auto-captured", you probably mean a hard crash (unhandled exception) that is captured with the crash reporting backend (by default breakpad on linux)?
Can you tell us which Sentry version you are running? There were a few changes to the "module finder" that captures these debug IDs recently. And are you running the app in a container?
Closing since there was no response for over a year. Feel free to reopen if the problem reoccurs.