Searched refs:why (Results 1 – 25 of 28) sorted by relevance
12
15 # TODO: Find out why this is happening.
20 # TODO: investigate why we need this.
84 # TODO: why is this so broad? Tightening candidate? It needs at list:
473 # TODO: Figure out why write is needed and remove.
945 -system_server # why?
26 void die(const char *why, ...) in die() argument30 va_start(ap, why); in die()32 vfprintf(stderr, why, ap); in die()
8 ….googlesource.com/platform/system/extras/+/master/simpleperf/doc/README.md#why-we-suggest-profilin…
14 --record_boot_reason Record the reason why the device booted
101 # TODO: why is this so broad? Tightening candidate? It needs at list:
503 # TODO: Figure out why write is needed.
1246 -system_server # why?
85 # TODO: why is this so broad? Tightening candidate? It needs at list:
483 # TODO: Figure out why write is needed.
938 -system_server # why?
110 # TODO: why is this so broad? Tightening candidate? It needs at list:
534 # TODO: Figure out why write is needed.
317 In most cases this message at the bottom is all that is needed to figure out why it failed.330 If it is still unclear why the failure is happening, the last thing to do is look
986 # in the section titled "A Short ROP Chain" for why.