You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, packaged pod-ui binaries are huge because they contain debugging info. Debugging info can be split off and packages only with debug build (needed?).
For the purpose of producing smaller release images, yet having the option of getting useful stack dumps (symbolicated, matched with source in sentry), this proved to work after much swearing and trying different approaches:
build release profile with debug info and thin LTO;
split-debuginfo=packed does not do much in Linux or mingw64 builds (rust updated to 1.67), so splitting debug info from executables on these platforms is accomplished using objcopy);
split-debuginfo=packed is mandatory in macOS to actually get debug symbols;
link-arg=-Wl,--build-id is needed in mingw64 for it does not automatically include build id;
sentry needs debug-images feature flag to be able to match stack traces to uploaded debug symbols;
sentry has problems recognizing split debug symbols in mingw64;
upload the executable, split debug symbols (.dSYM in macOS, .debug in Linux) and sources to sentry;
mingw64: upload the unstripped executable and sources to sentry, then strip debug symbols for release;
Currently, packaged pod-ui binaries are huge because they contain debugging info. Debugging info can be split off and packages only with debug build (needed?).
Needs testing, especially with sentry.
Resources:
The text was updated successfully, but these errors were encountered: