You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/error-reporting/troubleshooting.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ To resolve missing symbols, the first step is to identify which symbols are miss
70
70
71
71
Backtrace indicates that a crash report is missing symbols by setting an attribute, `_missing_symbols`, to 1, and in the debug view UI (in the callstack and the global annotations sections).
72
72
73
-
When a crash report is missing standard symbol files, in the debug view you'll see a memory address in the callstack with an orange triangle `missing symbol` icon.
73
+
When a crash report is missing standard symbol files, in the debug view, you'll see a memory address in the callstack with an orange triangle `missing symbol` icon.
@@ -92,7 +92,7 @@ Upon hover, you'll see a "missing CFI" message with details about the missing fi
92
92
93
93
If either of the filename or the debug ID are missing in this hover message, then you can search the global annotations modules section for whichever information (the debug ID or filename) was provided to find the missing portion from the corresponding symbol file entry.
94
94
95
-
These options should be sufficient in determining what symbols are missing from a crash report, but always feel free to reach out to our support team (by opening a support ticket, via the in-app widget, or emailing [email protected] for additional assistance.
95
+
These options should be sufficient in determining what symbols are missing from a crash report. [Contact our Support team](https://support.saucelabs.com/s/?language=en_US) if you need additional assistance.
96
96
97
97
### Supplying Missing Symbols
98
98
@@ -106,7 +106,7 @@ If you are uploading symbols manually, your next steps will be to retrieve and u
106
106
107
107
If you are using a [custom symbol server](/error-reporting/project-setup/symbolication/#integrate-custom-symbol-server-with-backtrace), then your next step will be to verify that the symbol exists on the symbol server in the proper directory structure (that is, `<url>/<object_name>/<debug_id>/<file>`). If it does not, then you know why it did not apply.
108
108
109
-
If it does exist, and reprocessing does not correct, then there are a few additional things to check. These items to check live in the symbol server section of your project settings (navigate from the **Main Menu** > **Project Settings** > **Symbols** > **Symbol Servers**), unless otherwise noted.
109
+
If it does exist and reprocessing does not correct it, then there are a few additional things to check. These items to check live in the symbol server section of your project settings (navigate from the **Main Menu** > **Project Settings** > **Symbols** > **Symbol Servers**), unless otherwise noted.
110
110
111
111
- White list: If this optional configuration is enabled, then a symbol's name must exist on the white list in order for Backtrace to download it from the symbol server.
112
112
- Skip list: Symbol name and debug ID combinations that fail to download from a custom symbol server are added to a skip list so that requests are not made for symbols which do not exist on the server. If a symbol that previously did not exist on the symbol server was uploaded, its name and debug ID may exist on this list. Removing the name and ID from the skiplist and reprocessing the crash object will allow the symbol to download. The symbols can removed from the skip list tab of the symbol server entry, or via our command line tool, [morgue](/error-reporting/advanced/morgue/).
@@ -136,7 +136,7 @@ You must have actually provided / uploaded the symbols in question. If you haven
136
136
137
137
Once missing symbols are uploaded or obtained from a symbol server, and the relevant crashes are reprocessed, the callstack will resolve completely.
138
138
139
-
If there are any questions or remaining issues, always feel free to reach out to our support team by opening a support ticket, via the in-app widget, or emailing [email protected].
139
+
[Contact our Support team](https://support.saucelabs.com/s/?language=en_US) if you need additional assistance.
140
140
141
141
## Why Are Aggregate Filters Removed In Certain Views?
0 commit comments