Contents

# Crash Report Tool

The Crash Report Tool starts automatically after a program crash occurs.

The Crash Report Tool gathers necessary information that can help the program developers to improve the code, so that in later versions this error can possibly be avoided. Please help us to improve the software and send the generated crash report.

## Starting the Crash Report Tool

With most program crashes the Crash Report Tool will start automatically.

## Sending the Crash Report

Select the checkbox if you want to restart LibreOfficeDev in safe mode. Then click the Send Crash Report button.

If a crash report is sent successfully, a dialog box will provide a URL for your report. To see the report, copy the URL and paste into a web browser.

You will not get an answer to your crash report. If you need support, please visit Community Assistance for an overview of different possibilities.

## What Data are Sent?

The crash report sends information about the error type that caused the crash and the process memory contents at the time of the crash. The memory contents include: a list of loaded libraries and their version number; a list of the current threads with the contents of their stack memory and processor register states. The memory trace is gathered locally by standard system tools: dbghelp.dll on Windows systems; clone(), ptrace() and /proc directory on Linux systems.

Information is also sent about the LibreOfficeDev version, the operating system name and version, and the computing hardware (CPU type and features; total RAM memory size; graphics device and driver).

The crash report is anonymous. No identification information is sent and no document content is sent. The report data are sent as a multipart HTTP POST request. See also the Privacy Policy - section I.XI

Vendors like Ubuntu or Apple package their own crash reporter in their version of LibreOfficeDev. No data is sent to The Document Foundation.

Please support us!