b8344dc72fde9386cdecbb1aa8a47f1e8e430111 |
|
25-Jan-2018 |
Yi Jin <jinyithu@google.com> |
Fix command line tool to set the right privacy enum. Test: manual Change-Id: I3f0845ea32b46f1a028f8b6d3d4180a90a47beb5
/frameworks/base/tools/incident_report/main.cpp
|
22769e0123340f49370ea4748aff71a1b84dc863 |
|
16-Oct-2017 |
Yi Jin <jinyithu@google.com> |
Fixed several bugs found for incidentd 1. Add logging for proto can't be parsed by incident_report 2. Close opened file descriptor of incident report request! 3. Fix invalid syntax of auto-gen section_list.cpp Bug: 67849582 Test: manually run incident and checks /proc/<its pid>/fd Change-Id: I38e6ac28de09aca6243ad536ed41d8059e08ba24
/frameworks/base/tools/incident_report/main.cpp
|
129fc6ce194659eed25fc37bb382eed61a14b7a7 |
|
29-Sep-2017 |
Yi Jin <jinyithu@google.com> |
Implement Activity Manager Broadcasts dump protos Bug: 66729158 Test: Manually build and flash the system.img and test "activity --proto broadcasts" Change-Id: I3cb7474c4a3ab092f38ed6a121b4d034cadfc402
/frameworks/base/tools/incident_report/main.cpp
|
ee6495982fb7b99dc90a52dc751ce4f7cae3fb9d |
|
05-Oct-2017 |
Kweku Adams <kwekua@google.com> |
incidentd: Fix printing of repeated scalar fields. Also add check for when enum value can't be found and fixing output formatting for some int types. BUG: 65633831 Test: check incident_report output of repeated enums. Change-Id: I329eef9b3bb0026259ea465ab67e71952df1a4e4
/frameworks/base/tools/incident_report/main.cpp
|
f32af48069f590a998f7dde188ea5afd3ffe2d96 |
|
12-Aug-2017 |
Yi Jin <jinyithu@google.com> |
Fix parsing enum types in incident report tool as well as adding some additional loggings Test: manually flashed to device and test calling IncidentManager.java functions Change-Id: I69610414edde865b20ba632837f037fbe43f99db
/frameworks/base/tools/incident_report/main.cpp
|
7a757a0f08eb3b1df8eb7ee2e915682ee4dca555 |
|
26-Jul-2017 |
Yunlian Jiang <yunlian@google.com> |
fix a memory leak. This fixes a memory leak warning: Potential leak of memory pointed to by 'buffer' [clang-analyzer-unix.Malloc] Bug:None Test: The warning is gone. Change-Id: I50bfd9f7d70964da0f1808b73fc6554831020214
/frameworks/base/tools/incident_report/main.cpp
|
89547ce0178d5b5b66badc5a422cdbecc9ddac34 |
|
01-Feb-2017 |
Yunlian Jiang <yunlian@google.com> |
fix some memory leaks. This fixes some warnings like warning: Potential leak of memory pointed to by 'target' [clang-analyzer-cplusplus.NewDeleteLeaks] Bug: None Test: The warnings are gone. Change-Id: I3708671bbc9965133439664b766df3236d1b01bf
/frameworks/base/tools/incident_report/main.cpp
|
7669012623a18855913c84ec0690066fbfd823ea |
|
20-Dec-2016 |
Joe Onorato <joeo@google.com> |
Clean up file names for protos Test: cts-tradefed run singleCommand cts -d --module CtsIncidentHostTestCases Change-Id: Iea2fc81768082e8e01afa8df86e113665020e7f6
/frameworks/base/tools/incident_report/main.cpp
|
1754d744a7a34731ffc07af1bc3dbfcb06864ab0 |
|
22-Nov-2016 |
Joe Onorato <joeo@google.com> |
First checkin of incident reporting. There are a few major pieces here: incidentd --------- This daemon (started by init) runs and accepts incoming requests to take incident reports. When prompted, it calls into various system services and fills in an IncidentProto data structure, and then writes the report into dropbox. The next steps for incidentd: - Security review of SELinux policies. These will be a subset of the dumpstate permissions. Until this is done, incidentd is not started at boot time. incident -------- This shell command calls into incidentd, and can initiate an incident report and either capture the output or leave for dropbox. incident_report --------------- This host side tool can call adb shell with the correct parameters and also format the incident report as text. This formatting code was left of the device on purpose. Right now it's pretty small, but as the number of fields increases, the metadata and code to do the formatting will start to grow. The incident_report command also contains a workaround to let it work before incidentd is turned on by default. Right now, it is implemented to call adb shell dumpsys <service> --proto directly, whereas in the future it will go through the full incidentd flow. incident_section_gen -------------------- A build-time tool that generates a stripped down set of information about the fields that are available. libincident ----------- This library contains the code to connect to incidentd, and the meta proto definitions that are used by the framework protos. The basics are here now, but they are not fully fleshed out yet. The privacy.proto file contains annotations that can go in the proto file that we will later use to filter which fields are uploaded, and which are used by local sources. For example, a device in a test lab is safe to upload much much more information than a real user. These will share the same mechanism, but the user's output will be filtered according to these annotations. frameworks/core/proto --------------------- These .proto files contain the definitions of the system's output. There is one master android.os.IncidentProto file that is the top level of an incident report, but some other services (notification, fingerprint, batterystats, etc) will have others that are used directly by the logging mechanism. Other files which are shared by several of the services also go here, such as ComponentName, Locale, Configuration, etc. There will be many more. There is also a first iplementation of a dump method handling --proto in the fingerprint service. IncidentManager --------------- The java API to trigger an incident report. Test: Not written yet Change-Id: I59568b115ac7fcf73af70c946c95752bf33ae67f
/frameworks/base/tools/incident_report/main.cpp
|