uReport description¶

ABRT supports uReports for four types of crashes: crashes of C/C++ programs that result in a core dump, uncaught Python exceptions, uncaught Java exceptions and kernel oopses.

Each uReport generally contains a stack trace, or multiple stack traces in the case of multi-threaded C/C++ and Java programs. The stack trace only describes the call stack of the program at the time of the crash and does not contain contents of any variables.

Every uReport also contains identification of the operating system, versions of the RPM packages involved in the crash, and whether the program ran under a root user.

There are also items specific to each crash type:

C/C++ crashes

Python exceptions

for kernel oopses

The authenticated uReports also contains hostname and machineid to enable a server side filtering at https://access.redhat.com/.

The authenticated uReports have the benefit of rich server replies which may include a solution for the submitted crash. The authentication is done using either Red Hat Subscription Certificates or Red Hat Customer Portal credentials.

Warning: The full text of a kernel oops might contain information like the identification of the host hardware type. You should disable the autoreporting feature if you do not want to share this information with Red Hat.