mirror/tracy
1
0
Fork 0
mirror of https://github.com/wolfpld/tracy.git synced 2024-09-20 05:42:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Crash handling works on android.

Browse Source
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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
NEWS
View File

@ -102,7 +102,7 @@ v0.4 (xxxx-xx-xx)
processor, a message dialog with workaround instructions will be processor, a message dialog with workaround instructions will be
displayed. displayed.
- Tracy can intercept crashes and finish sending data from a dying process. - 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 - Call stack window may now display addresses of the frames, instead of
source file locations. source file locations.

2
manual/tracy.tex
View File

@ -284,7 +284,7 @@ Be aware that even if you already have thread naming functionality implemented,
\subsection{Crash handling} \subsection{Crash handling}
\label{crashhandling} \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. This is an automatic process and it doesn't require user interaction.