Skip to content

Commit 72bfde4

Browse files
committed
Fixed readme conflict
1 parent cfcf69a commit 72bfde4

File tree

1 file changed

+3
-32
lines changed

1 file changed

+3
-32
lines changed

README.md

Lines changed: 3 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -129,20 +129,19 @@ The following is a reference guide to the Backtrace Client fields:
129129
- Retry interval: If the database is unable to send its record, this setting specifies how many seconds the library should wait between retries.
130130
- Maximum retries: If the database is unable to send its record, this setting specifies the maximum number of retries before the system gives up.
131131
- Retry order: This specifies in which order records are sent to the Backtrace server.
132-
133132
# Android Specific information
134133

135134
The backtrace-unity library includes support for capturing additional Android Native information, from underlying Android OS (Memory and process related), JNI, and NDK layers.
136135

137136
## Native process and memory related information
138137

139-
system.memory usage related information including memfree, swapfree, and vmalloc.used is available. Additional VM details and voluntary / nonvountary ctxt switches are included.
138+
system.memory usage related information including memfree, swapfree, and vmalloc.used is now available. Additional VM details and voluntary / nonvountary ctxt switches are included.
140139

141140
## ANR
142141

143-
When configuring the backtrace-unity client for an Android deployment in the Unity Editor, programmers will have a toggle to enable or disable `ANR reports`. This will use the default of 5 seconds.
142+
When configuring the backtrace-unity client for an Android deployment, programmers will have a toggle available in backtrace-unity GUI in the Unity Editor to enable or disable ANR reports. This will use the default of 5 seconds.
144143

145-
## Debug Symbol upload
144+
## Symbols upload
146145

147146
Unity allows developer to generate symbols archive called `symbols.zip` in the il2cpp build pipeline in the root directory of your game. In this archive you can find generated symbols for your game libraries. When your game crashes due to a native exception, your stack trace will contain only memory addresses instead of function name. Symbols from `symbols.zip` archive allows Backtrace to match function address to function name in your source code.
148147

@@ -361,34 +360,6 @@ Notes:
361360
- `BacktraceDatabase` `Count` method will return number of all records stored in database (included deduplicated records),
362361
- `BacktarceDatabase` `Delete` method will remove record (with multiple deduplicated records) at the same time.
363362

364-
<<<<<<< HEAD
365-
=======
366-
# Android Specific information
367-
368-
The backtrace-unity library includes support for capturing additional Android Native information, from underlying Android OS (Memory and process related), JNI, and NDK layers.
369-
370-
## Native process and memory related information
371-
372-
system.memory usage related information including memfree, swapfree, and vmalloc.used is now available. Additional VM details and voluntary / nonvountary ctxt switches are included.
373-
374-
## ANR
375-
376-
When configuring the backtrace-unity client for an Android deployment, programmers will have a toggle available in backtrace-unity GUI in the Unity Editor to enable or disable ANR reports. This will use the default of 5 seconds.
377-
378-
## Symbols upload
379-
380-
Unity allows developer to generate symbols archive called `symbols.zip` in the il2cpp build pipeline in the root directory of your game. In this archive you can find generated symbols for your game libraries. When your game crashes due to a native exception, your stack trace will contain only memory addresses instead of function name. Symbols from `symbols.zip` archive allows Backtrace to match function address to function name in your source code.
381-
382-
To generate `symbols.zip` archive make sure:
383-
* you selected il2cpp build,
384-
* you checked `Create symbols.zip` in the Build settings window
385-
![Create symbols.zip](./Documentation~/images/symbols.png)
386-
387-
To upload symbols to Backtrace, you need to rename symbols generated by Unity end simply with a `.so` extension. By default, symbol files within the .zip will end with extension `.sym.so`. or `.dbg.so` Backtrace will only match symbols to files based on the ending with `.so` extension. Please ensure all files have a single `.so` extention before uploading the zip. To upload symbols please go to your project settings, to the `Upload an archive` tab under `Symbols` section.
388-
389-
Backtrace offers to upload symbols automatically from Unity Editor to your Backtrace instance. Backtrace symbols upload pipeline will be triggered after successfull build of il2cpp Android game and when Symbols upload token is available in Backtrace Client options. After successfull build, upload pipeline will confirm symbols upload.
390-
391-
>>>>>>> feature/uname-update
392363
# Architecture description
393364

394365
## BacktraceReport <a name="architecture-BacktraceReport"></a>

0 commit comments

Comments
 (0)