Crash handling works on android.

This commit is contained in:
Bartosz Taudul 2018-08-27 14:08:54 +02:00
parent 2ebe9b72d1
commit 8ab3409266
2 changed files with 2 additions and 2 deletions

2
NEWS
View File

@ -102,7 +102,7 @@ v0.4 (xxxx-xx-xx)
processor, a message dialog with workaround instructions will be
displayed.
- Tracy can intercept crashes and finish sending data from a dying process.
- Currently this is only implemented on Windows and Linux.
- Currently this is only implemented on Windows, Linux and Android.
- Call stack window may now display addresses of the frames, instead of
source file locations.

View File

@ -284,7 +284,7 @@ Be aware that even if you already have thread naming functionality implemented,
\subsection{Crash handling}
\label{crashhandling}
On selected platforms\footnote{Windows, Linux.} Tracy will intercept application crashes\footnote{For example, invalid memory accesses ('segmentation faults', 'null pointer exceptions'), divisions by zero, etc.}. This serves two purposes. First, the client application will be able to send the remaining profiling data to the server. Second, the server will receive a crash report with information about the crash reason, call stack at the time of crash, etc.
On selected platforms\footnote{Windows, Linux and Android.} Tracy will intercept application crashes\footnote{For example, invalid memory accesses ('segmentation faults', 'null pointer exceptions'), divisions by zero, etc.}. This serves two purposes. First, the client application will be able to send the remaining profiling data to the server. Second, the server will receive a crash report with information about the crash reason, call stack at the time of crash, etc.
This is an automatic process and it doesn't require user interaction.