summaryrefslogtreecommitdiff
path: root/libunwindstack/tests/MemoryFileTest.cpp
diff options
context:
space:
mode:
authorElliott Hughes <enh@google.com>2016-10-19 14:47:11 -0700
committerElliott Hughes <enh@google.com>2016-10-21 14:22:40 -0700
commitcabfa1177f11772e29229135d08b1034518cad93 (patch)
tree1ed2f7938bcd1fa6b077306c66a7ed9ff973dd5f /libunwindstack/tests/MemoryFileTest.cpp
parentc741dd48385a84161c23d7a2684e06cbfc7646a8 (diff)
Move "adb shell" over to getopt(3), and allow -tt on old devices.
From the bug: Say we run a new adb against an old device (like KitKat). Even with a new client ADB, in this configuration, "adb shell" will create a remove tty unconditionally. So if the user runs "adb shell -t -t", we shouldn't fail with a message about the remote device not supporting -tT options --- the user asked to create a tty unconditionally, and since we're going to create a tty unconditionally, we should just succeed. (That it's going to succeed due to protocol inadequacy instead of succeeding on purpose is irrelevant.) That adb fails in this case makes scripts more complicated, since they can't just pass "-t -t" unconditionally if they want a tty and to work on all device versions, even if the script requires a new-ish adb locally. Bug: http://b/32216152 Bug: http://b/32219151 Test: test_device.py Change-Id: I8ab7c8dfa212209a7ab43c1f0832eeac26d2e42f
Diffstat (limited to 'libunwindstack/tests/MemoryFileTest.cpp')
0 files changed, 0 insertions, 0 deletions