Problem Statement

The F.O.S.S. Mudlet MUD Client has recently adopted Sentry as a means to marshal information about problems with our product. We compile its Windows builds in a MSYS2+Mingw-w64 environment - as such we've been using a GCC compiler which is not (AFAICT) capable of generating "debug" information in the Windows .pdb format. I am aware that we could switch to the LLVM clang alternative and get the wanted symbols by providing -g -gcodeview as compiler options. However the upstream's debug symbols for the packages that we link to are provided only as separate .debug files - so that automatically prevents issues in code that we do not author from being properly handled by Sentry.

My apologies for not bringing this up as a Discussion as your contribution guide suggests but I could not see any discussion where this would fit.

Solution Brainstorm

Is there any way that Sentry could have the option to handle GCC .debug debug symbol files for Windows applications in the same manner that it does for GNU/Linux ones?

Product Area

Unknown