Andrew McKnight

Correct.

The profiler currently will collect backtraces per thread on a sampling interval: https://github.com/getsentry/sentry-cocoa/blob/e3d2bc4d5bf2c6d8d4f47ba4537936a8286fb05e/Sources/Sentry/SentryProfiler.mm#L151 and https://github.com/getsentry/sentry-cocoa/blob/e3d2bc4d5bf2c6d8d4f47ba4537936a8286fb05e/Sources/Sentry/SentrySamplingProfiler.cpp#L51 Each backtrace has a time appended to it, and we postprocess this in the backend...

Hi @shwetashendage, I'm curious to know more about your use case. Do you have one org with two different projects, or do you want to send these events to projects...

@jaroslavas Could you provide a full crash report for some of these examples? There should be a thread that is indicated as the "Crashed thread", and maybe other info like...

Looking again at the stack trace, the app has already crashed for some reason, as our signal handler is running (`onCrash`). However, the fact that `_dyld_get_image_header` takes a lock is...

Hmm just occurred to me that setting `debug` to false after setting `diagnosticLevel` will overwrite it to `error` again. That needs to be fixed. `diagnosticLevel` probably shouldn’t even be exposed...

@brustolin @bruno-garcia I just wanted to confirm that this change in behavior is desired. I was fixing the broken tests and noticed that one is `testConfigureWithoutDebug_PrintsNothing`, which tells me that...

You have a point about end users, that would require a more integrated approach. This would be immediately helpful for any other build that doesn't set debug to true, that...

@brustolin I updated the doc comment in SentryOptions, but that led me to make a few other changes after thinking about things some more. I deprecated `diagnosticLevel` so most of...

I think this should be closed now, now that we've discussed the philosophy behind how we do logging. Nothing is actually broken there, so shouldn't be messed with.