Add sentry.io crash logger to Qt Creator

What is the benefit? Why is this valuable?

Make it possible to understand user crashes via logged evidence.

With harvested evidence it is more straightforward to reproduce, analyze and fix bugs.

The importance increases on account of the extension model, as a crash in an extension will affect Qt Creator as well, and the contributors may be unaware of the issue.

Enables post mortem analysis of Design Studio as well.

What are common use cases?

While manual reporting via Jira, accompanied with discussions with the author shall be the primary investigation channel, automated reporting extends the audience to cover situations where the user is unaware why the Qt Creator crashed.

Qt Creator user is requested permission to relay crash information to Qt (privacy-consciousness).

Qt Creator user experiences a crash in the tool and submits the crash info to the sentry service.

The R&D team members utilize the harvested information to analyze the crash and fix the issue that is the root cause.

In case of the crash occurring in context of an extension, the contributor of a crashing extension is notified about the issue.

​

​

Technical information

Use sentry.io to facilitate the harvesting and analysis of post mortem information.

Evaluate how the sentry.io can be integrated with the tools used (Jira, Teams, git).

​