koopajah

I remember trying multiple solutions with exception files and such but not having a lot of luck at filtering the ones I did not care about while keeping my own errors displayed. It's clearly user error on my end but I always gave up and rewrote smaller samples without external dependency when I could.

I love valgrind and it saved my ass countless time when tracking memory leaks or overflows. The main issue I've always had with it is filtering the output easily. When you use external libraries (portaudio or Qt for example but also proprietary libraries I had to use at work) a lot of the debug messages pollute what is really yours and your leak is then a needle in a haystack.

I've encountered a lot of issues on Windows XP with QT/Angle but also quite a lot on Windows Vista/7 where the graphic drivers by default don't support properly OpenGL or pretend they do but don't answer properly to Qt's requests. This ended up with a big chunk of my users having a blank window or even no window displayed to them and no way to reliably detect this on our end.

This feature has been in the works for multiple months now and I'm really glad to finally see it ship officially with Qt 5.4, so congrats to the team!