Name |
Date |
Size |
#Lines |
LOC |
||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| .clang-format | D | 23-Mar-2024 | 288 | 14 | 12 | |
| Android.bp | D | 23-Mar-2024 | 605 | 45 | 36 | |
| AndroidTest.xml | D | 23-Mar-2024 | 1.2 KiB | 27 | 12 | |
| OWNERS | D | 23-Mar-2024 | 89 | 7 | 5 | |
| bugreportz.cpp | D | 23-Mar-2024 | 2.3 KiB | 76 | 44 | |
| bugreportz.h | D | 23-Mar-2024 | 843 | 23 | 4 | |
| bugreportz_test.cpp | D | 23-Mar-2024 | 4 KiB | 129 | 81 | |
| main.cpp | D | 23-Mar-2024 | 3.3 KiB | 114 | 72 | |
| readme.md | D | 23-Mar-2024 | 749 | 21 | 14 |
readme.md
1 # bugreportz protocol 2 3 `bugreportz` is used to generate a zippped bugreport whose path is passed back to `adb`, using 4 the simple protocol defined below. 5 6 # Version 1.1 7 On version 1.1, in addition to the `OK` and `FAILURE` lines, when `bugreportz` is invoked with 8 `-p`, it outputs the following lines: 9 10 - `BEGIN:<path_to_bugreport_file>` right away. 11 - `PROGRESS:<progress>/<total>` as `dumpstate` progresses (where `<progress>` is the current 12 progress units out of a max of `<total>`). 13 14 ## Version 1.0 15 On version 1.0, `bugreportz` does not generate any output on `stdout` until the bugreport is 16 finished, when it then prints one line with the result: 17 18 - `OK:<path_to_bugreport_file>` in case of success. 19 - `FAIL:<error message>` in case of failure. 20 21