You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
hmz007 36ed224bac
Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a)
1 year ago
..
.clang-format Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
Android.bp Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
AndroidTest.xml Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
OWNERS Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
bugreportz.cpp Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
bugreportz.h Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
bugreportz_test.cpp Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
main.cpp Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
readme.md Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago

readme.md

bugreportz protocol

bugreportz is used to generate a zipped bugreport whose path is passed back to adb, using the simple protocol defined below.

Version 1.1

On version 1.1, in addition to the OK and FAILURE lines, when bugreportz is invoked with -p, it outputs the following lines:

  • BEGIN:<path_to_bugreport_file> right away.
  • PROGRESS:<progress>/<total> as dumpstate progresses (where <progress> is the current progress units out of a max of <total>).

Version 1.0

On version 1.0, bugreportz does not generate any output on stdout until the bugreport is finished, when it then prints one line with the result:

  • OK:<path_to_bugreport_file> in case of success.
  • FAIL:<error message> in case of failure.