Sign up for the KDAB Newsletter
Stay on top of the latest news, publications, events and more.
Go to Sign-up
Find what you need - explore our website and developer resources
4 October 2022
Your Qt / C++ application is feature complete, you fixed all the bugs, and your unit-tests pass! Time to ship it and get on with your life. Unfortunately, then you start to get reports that it crashes for some people, sometimes, on some machines. But they can’t remember what they were doing. Or know what version they were running. Or whether they’re running macOS or Windows.
In this session, we’ll look at my experiences adding real-time automated crash- and error-reporting to a large open-source application, and what I learned in the process. We’ll consider correlating manual user feedback (bug reports) with automated feedback, and adding tracing to our application workflow to understand the steps leading up to an error.
We’ll also review the build and tooling changes required for crash reporting, and integration with other systems, and some other interesting metrics we obtain from the system.
All QtDevCon22 Videos: https://www.youtube.com/playlist?list=PL6CJYn40gN6h5jKSLw0cEsKficprxd2iX
QtDevCon22 Website:
https://www.qtdevcon.com/
Every month our newsletter is featuring technical blogs on Qt, C++ and 3D topics: https://www.kdab.com/newsletter/
Stay on top of the latest news, publications, events and more.
Go to Sign-up
Learn Modern C++
Our hands-on Modern C++ training courses are designed to quickly familiarize newcomers with the language. They also update professional C++ developers on the latest changes in the language and standard library introduced in recent C++ editions.
Learn more