Crashpad reports appear much worse on Linux
Looking at Sentry, the crash reports sent from Linux machines seem fairly useless compared to the same reports sent from Windows machines. An example is https://github.com/vircadia/vircadia/issues/1542. The Linux crash reports seem pretty unspecific, while the Windows crash report tells us immediately where the issue occurs.
@ksuprynowicz suggested that this might be because of the optimization flags. If this is true we should find out which optimization(s) is(are) causing this exactly and disable them.
If we decide to disable optimizations, we need to see what is the performance impact. Building with full optimizations but with -g3 flag might be a good alternative.
We already know if runs like trash without optimizations. I guess we should try the -g3 flag then. And with we I mean probably me.
Hello! Is this still an issue?