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/RFCs/0011-crashtracker-structured-log-format-V1_X.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,6 +78,8 @@ Consumers of the crash data format SHOULD be designed to handle all versions fro
78
78
-`stack`: **[required]**
79
79
This represents the stack of the crashing thread.
80
80
See below for more details on how stacktraces are formatted.
81
+
-`thread_name`: **[optional]**
82
+
Name of the crashing thread
81
83
-`files`: **[optional]**
82
84
A `Map<filename, contents>` where `contents` is an array of plain text strings, one per line.
83
85
Useful files for triage and debugging, such as `/proc/self/maps` or `/proc/meminfo`.
@@ -273,6 +275,15 @@ This section documents the evolution of the crashtracker structured log format a
273
275
274
276
**Motivation:** When symbol names are demangled for readability, the original mangled names are lost. This makes debugging difficult when mangled names are needed (e.g., comparing against compiler-generated symbols). The `mangled_name` field preserves the original mangled name when demangling occurs.
275
277
278
+
### Version 1.5
279
+
*Added thread_name to `ErrorData`
280
+
281
+
**Changes from v1.4:**
282
+
- Added `thread_name` field to `Error` objects (optional string)
283
+
- Updated `data_schema_version` to "1.5"
284
+
285
+
**Motivation:** Having access to thread name of the crashing thread helps debugging, especially within multithreaded programs.
286
+
276
287
## Appendix A: Example output
277
288
278
289
An example crash report in version 1.0 format is [available here](artifacts/0005-crashtracker-example.json).
@@ -281,7 +292,7 @@ Note: This example uses version 1.0 format. Version 1.1+ may include additional
281
292
282
293
## Appendix B: Json Schema
283
294
284
-
The current JSON schema (version 1.4) is [available here](artifacts/0009-crashtracker-schema.json).
295
+
The current JSON schema (version 1.5) is [available here](artifacts/crashtracker-unified-runtime-stack-schema-v1_5.json).
0 commit comments