Searched refs:print_point (Results 1 – 2 of 2) sorted by relevance
35 4. `print_logs BUFFER_TYPE [buffers] [print_point]` - this prints the logs as processed by the given37 `print_point` have been logged. This acts as if a user called `logcat` immediately after the43 `print_point` is an positive integer. If it is unspecified, logs are printed after the entire
303 const char* print_point) in PrintLogs() argument306 if (print_point != nullptr) { in PrintLogs()308 if (!ParseUint(print_point, &result)) { in PrintLogs()309 fprintf(stderr, "Could not parse print point '%s'\n", print_point); in PrintLogs()