[Android-tools-devel] Bug#738128: I believe that newer version of adb resolve this issue.

Kan-Ru Chen (=?UTF-8?Q?=E9=99=B3=E4=BE=83=E5=A6=82?=) kanru at kanru.info
Tue Oct 20 09:55:30 UTC 2015


Oleksandr Gavenko <gavenkoa at gmail.com> writes:

> When compare:
>
>   $ strace -o ~/tmp/adb.log adb devices
>
> and:
>
>   $ strace -f -o ~/tmp/adb2.log /opt/android-sdk-linux/platform-tools/adb devices
>
> the difference:
>
>   socket(PF_LOCAL, SOCK_STREAM, 0)  = 3
>   connect(3, {sa_family=AF_LOCAL, sun_path="/tmp/5037"}, 12) = 0
>   write(3, "000c", 4)               = 4
>   write(3, "host:version", 12)      = 12
>   read(3, "OKAY", 4)                = 4
>   read(3, "0004", 4)                = 4
>   read(3, "001f", 4)                = 4
>   close(3)                          = 0
>
> and:
>
>   write(1, "List of devices attached\n", 25) = 25
>   socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
>   connect(3, {sa_family=AF_INET, sin_port=htons(5037), sin_addr=inet_addr("127.0.0.1")}, 16) = 0
>   write(3, "000c", 4)               = 4
>   write(3, "host:version", 12)      = 12
>   read(3, "OKAY", 4)                = 4
>   read(3, "0004", 4)                = 4
>   read(3, "0020", 4)                = 4
>   close(3)                          = 0
>
> So newer version doesn't used file sockets for awaiting client connection.
>
> I believe that newer version of adb resolve this issue. Waiting for new
> version.

The Debian version is patched to use local socket transport by default
so I think the newer version doesn't resolve this issue, unfortunately.

   Kanru



More information about the Android-tools-devel mailing list