Searched refs:debugging (Results 1 – 25 of 34) sorted by relevance
12
11 # Keep names for easy debugging.14 # Necessary to allow debugging.
12 7) [Debugging in the Shell](debugging.md)
85 More detail can be found in [Debugging in the Shell](debugging.md) section.
8 debugging problems that arise (especially in dogfood). The Shell uses the same efficient Protolog
16 # debugging stack traces.
17 using the build system. This is useful for debugging the tool.
43 // for debugging a failure. If you are trying to diagnose how a crash was
4 To test on physical devices, connect _two_ devices locally and enable USB debugging setting on both…
47 // Store test artifacts in separated directories for easier debugging.
36 This function is intended for debugging only and should not be used in shipping
26 // permission for the purpose of debugging photos.
45 …/bcc {{.*}}VERSIONDOESNOTEXIST, expecting {{[1-9]+.[0-9]+.[0-9]+.*}}The debugging experience may b…46 ; CHECK_BCC_NOWARNING-NOT: W/bcc {{.*}}The debugging experience may be unreliable
83 // for debugging a failure. If you are trying to diagnose how a crash was
18 When debugging failures, the "-v" option will print to stdout the details of
8 # constructor. We also keep callback class names for easier debugging.
66 // message for debugging if there is an error.
42 …ard logs that will print to logcat. Should only be used temporarily for debugging. See [KeyguardCo…
258 // but is not authorized to be used outside of debugging.
24 2. Enable the Window Orientation Listener debugging data log.
1083 void setDebugging(boolean debugging) { in setDebugging() argument1084 mDebugging = debugging; in setDebugging()1085 mWindowProcessController.setDebugging(debugging); in setDebugging()
4 # Preserve line number information for debugging stack traces.
37 * This function is intended for debugging only and should not be used in shipping
142 for debugging purposes.
49 …re is a focused application. This is used by InputDispatcher purely for ANR and debugging purposes.