adbconnection: silence logspam.
Userdebug devices enable JDWP for every process, so if adbd is turned off manually, we get an error message for every single process on the system. Bug: http://b/154319466 Test: manual Change-Id: Ia702974d371e35497573c31e22cfb2b572334590
This commit is contained in:
parent
04e9d07490
commit
d81a805a4c
1 changed files with 7 additions and 1 deletions
|
|
@ -140,7 +140,13 @@ AdbConnectionClientContext* adbconnection_client_new(
|
|||
|
||||
int rc = connect(ctx->control_socket_.get(), reinterpret_cast<sockaddr*>(&addr), addr_len);
|
||||
if (rc != 0) {
|
||||
PLOG(ERROR) << "failed to connect to jdwp control socket";
|
||||
if (errno == ECONNREFUSED) {
|
||||
// On userdebug devices, every Java process is debuggable, so if adbd is explicitly turned
|
||||
// off, this would spew enormous amounts of red-herring errors.
|
||||
LOG(DEBUG) << "failed to connect to jdwp control socket, adbd not running?";
|
||||
} else {
|
||||
PLOG(ERROR) << "failed to connect to jdwp control socket";
|
||||
}
|
||||
return nullptr;
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue