GitXplorerGitXplorer
m

GdbCrashHandler

public
14 stars
8 forks
4 issues

Commits

List of commits on branch master.
Unverified
ea2e7b677c4e33a1f2ce554c620d0b7b9b6242f3

Port to quazip-1.x

mmanisandro committed 3 years ago
Unverified
e1399f877e98382178855604c26aaf69c22fdbc9

Bump version

mmanisandro committed 5 years ago
Unverified
afe330d7acf907a7dd9b6467312f2bb05d7d7911

Ensure stacktrace.txt is readable in zip

mmanisandro committed 5 years ago
Unverified
fde027086ce1924ca6d86f10dda3b3a3c568bde5

Update version

mmanisandro committed 5 years ago
Unverified
9fb028dead3d02ccac01da92c2dab30d4db9ed14

Add dist rule

mmanisandro committed 5 years ago
Unverified
94fb81063995513a59a1feb06775754ebc8123d5

Fix invalid indexOf test

mmanisandro committed 5 years ago

README

The README file for this repository.

GdbCrashHandler

A CrashRpt inspired CrashHandler for Qt based applications which attaches gdb to the dying process, collects a stacktrace and submits it to a web service.

It works by spawing a QProcess in the signal handler, re-starting the application with arguments --crashhandle <pid>, at which point GdbCrashHandler takes over.

screenshot

Usage:

Initialize the crash handler just after the QApplication instance has been created:

GdbCrashHandler::Configuration config;
config.applicationName = "CrashExample";
config.applicationVersion = "1.0";
config.applicationIcon = ":/icons/bug.png";
config.submitMethod = GdbCrashHandler::Configuration::SubmitService;
config.submitAddress = "http://127.0.0.1/report.php";
GdbCrashHandler::init(config, /*optional*/ fileSaveCallback);

See example/example.cpp.

Submit service:

GdbCrashHandler submits the reports to a web service, using the same format as CrashRpt, see service/report.php.