mystiq/rageshake
Archived
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Combine eleweb/eledesktop, add notes about process/thread ID.

Browse source
This commit is contained in:
Michael Kaye 2022-01-21 11:48:40 +00:00
parent bbe36198b7
commit e5a067b4b9
1 changed files with 7 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
docs/submitted_reports.md
View file

@ -2,15 +2,13 @@
Rageshakes can come from a number of applications, and we provide some practical notes on the generated format. Rageshakes can come from a number of applications, and we provide some practical notes on the generated format.
At present these should not be considered absolute nor a structure to follow; but an attempt to document the At present these should not be considered absolute nor a structure to follow; but an attempt to document the currently visible formats as of January 2022.
currently visible formats as of January 2022.
## Feedback ## Feedback
Log files are not transmitted; the main feedback is entirely within the user message body. Log files are not transmitted; the main feedback is entirely within the user message body.
## Element Web ## Element Web / Element Desktop
Log files are transmitted in reverse order (0000 is the youngest) Log files are transmitted in reverse order (0000 is the youngest)
@ -24,19 +22,12 @@ L = log level, (W=Warn, I=Info, etc)
New log files are started each restart of the app. New log files are started each restart of the app.
## Element desktop
## Element iOS ## Element iOS
Crash Log is special and is sent only once (and deleted on the device afterwards) Crash Log is special and is sent only once (and deleted on the device afterwards)
`crash.log` `crash.log`
Following logs are available, going back in time with ascending number. Following logs are available, going back in time with ascending number.
console.log with no number is the current log file. console.log with no number is the current log file.
``` ```
@ -64,18 +55,21 @@ Log file 0000 is odd, it contains the logcat data if sent.
Log line format: Log line format:
``` ```
01-17 14:59:30.657 14303 14303 W Activity: Slow Operation: 01-17 14:59:30.657 14303 14303 W Activity: Slow Operation:
<-- TIMESTAMP ---> <-?-> <-?-> L <-- Message -- <-- TIMESTAMP ---> <-P-> <-T-> L <-- Message --
L = Log Level (W=Warn, I=Info etc) L = Log Level (W=Warn, I=Info etc)
P = Process ID
T = Thread ID
``` ```
Remaining log files are transmitted according to their position in the round-robin logging to file - there will be (up to) 7 files written to in a continious loop; one of the seven will be the oldest, the rest will be in order. Remaining log files are transmitted according to their position in the round-robin logging to file - there will be (up to) 7 files written to in a continious loop; one of the seven will be the oldest, the rest will be in order.
Log line format: Log line format:
``` ```
2022-01-17T13:06:36*838GMT+00:00Z 12226 D/ /Tag: Migration: Importing legacy session 2022-01-17T13:06:36*838GMT+00:00Z 12226 D/ /Tag: Migration: Importing legacy session
< ---- TIMESTAMP ---------------> <-?-> L <-- Message ---- < ---- TIMESTAMP ---------------> <-P-> L <-- Message ----
L = log level, (W=Warn, I=Info, etc) L = log level, (W=Warn, I=Info, etc)
P = Process ID
``` ```
Once the fix to #40 is in place, we will see the following files: Once the fix to #40 is in place, we will see the following files: