Quality/QA-tools/CrashReporter

Crash Reporter is a test tool which uploads rich core dumps to Crash Analysis Service. It is part of MeeGo Crash Analysis Solution. Crash Reporter consists of the following components: Daemon, Auto Uploader, Crash Reporter UI, and Crash Reporter Settings Applet.

Contents 1 Components 1.1 Daemon 1.2 Auto Uploader 1.3 Crash Reporter UI 1.4 Crash Reporter Settings Applet

Components

Daemon

The Daemon monitors the known rich-core dump locations. When daemon detects the appearance of a new dump and notifications are enabled, it launches Crash Reporter UI, so that the user gets notified about the event and can decide what to do with the dump. When automatic uploading is enabled in the settings, Crash Reporter Auto Uploader will be launched and the user will not be notified. Additionally, this daemon implements an RPC interface for controlling rich-core monitoring and for fetching unsent dumps from the system. This daemon has no command line options. The preferred way of controlling whether notifications are displayed or not (other than uninstalling) is to use the Crash Reporter Settings applet in Control Panel.

Auto Uploader

The Crash Reporter Auto Uploader is a D-Bus service that is started by Crash Reporter Daemon when the automatic uploading is enabled in Crash Reporter settings and rich-core dumps are found on the system. The Auto Uploader tries to upload rich-core dumps to Crash Analysis Service, but it requires an open or automatic internet access point to function. If an internet connection cannot be opened automatically, Auto Uploader will not open any connectivity dialogs. It will however try to upload all existing rich-core dumps when a new dump appears. Automatic uploading can be enabled from the Crash Reporter settings applet.

Crash Reporter UI

Crash Reporter UI provides a user-friendly graphical user interface for sending and deleting rich-core dumps. It is started by Crash Reporter Daemon after device boot up, if there are unsent rich-core dumps in the the system and triggers a notification. If the user interacts with the notification (within a certain period of time) a dialog is displayed. User has the following options:

• Send selected Select rich-core dumps to be sent to a Crash Reporter Service. Selected files are deleted from the system after a successful upload.

• Send All Send all rich-core dumps to the service. Successfully uploaded files will be deleted.

• Delete selected The user can select rich-core dumps to be deleted from the system. Other than the selected files will not be affected and they can be dealt with later.

• Ignore Do nothing. The dialog will close down, leaving the dumps untouched. Unless the dumps are destroyed manually, the UI will start up after next reboot and ask the user again what to do with the dumps. The same dialog can also be accessed from the Control Panel.

The second use case when Crash Reporter UI is started by Crash Reporter Daemon is when rich-core dumps appear in the known dumping locations. When a signal is received, it triggers a notification. If the user interacts with the notification (within certain amount of time) a dialog is displayed. User has the following options:

• Send Uploads the current rich-core dump to the Crash Reporter Service. The file is deleted from the system after a successful upload.

• Delete The current rich-core dump is deleted from the system.

• Options Launches Crash Reporter Settings Applet for modifying Crash Reporter settings.

• Ignore Do nothing. The dialog will close down, leaving the dump untouched. Unless the dump is destroyed manually, the UI will start up after next reboot and ask the user again what to do with the dump.

Additionally, the UI allows user to enter a brief note containing background information about the situation where the crash occurred.

Crash Reporter Settings Applet

Crash Reporter Settings Applet is a Control Panel applet for enabling/disabling notifications, enabling automatic uploading and sending or deleting rich-core dumps found on the system. Additionally, some options controlling the information stored in the dumps by the rich-core-dumper can be configured here. These changes only affect subsequent dumps however.