Arpad Borsos
Arpad Borsos
May I ask which part exactly you want to package? In either case, I think one binary artifact that we ship is symbolic-cabi as part of the python package. Also...
(Without having checked), I think this comes from `criterion`, same as the Rust SDK. So we can ignore this for now, as its only a dev-dependency.
Indeed, this is not an issue upstream. I suspect because upstream has some tighter limits around recursion (both parsing as well as pretty printing). We had to increase those limits...
Interesting. The problem does not seem to be the pretty printing, but rather some part of the parsing. Even when I reset the recursion depth back to the default of...
Ideally symbolic would be independant of the underlying object parsing library, meaning that we shouldn’t expose that. Exposing that also means its types become part of our public API, meaning...
I think that is rather a grouping concern, and not about unwinding the call stack. We do want to have `KiUserExceptionDispatch` in the call stack, as it is probably also...
Didn’t I open this as a draft? I’m not convinced this is the way forward, as the only place this is effectively used is when printing things in sentry-cli. Can...
The only usage (for now) is via `chrono` which is also flagged in #492 itself.
This is also being used in `anylog` and `apple-crash-report-parser`, which are both sentry libraries.
I don’t really find anything for this. llvm seems to hardcode the whole `Ua9enable_ifI` part and match on that. No idea where that is coming from.