[Android-tools-devel] Bug#848852: adb command error with backtrace

[Senthil Kumaran S]

On Tuesday 20 December 2016 02:51 PM, Hans-Christoph Steiner wrote:
> I can't reproduce these on my stretch amd64 chroot, adb works fine for
> me.  So we'll need to figure how what in the environment is triggering
> the issue.  Are all the machines mentioned here ARM? Or what arches?

All these machines are amd64.

> For "adb: symbol lookup error: adb: undefined symbol: kFeatureShell2",
> my guess is that your android-libadb package has a different version
> than your adb package.  They should all have an exact matching upstream
> version (7.0.0+r1). Can you include the output of this:

I had android-tools-adb installed previously in this machine. I did the
following to upgrade:

$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo apt-get purge android-tools-adb
$ sudo apt-get install adb

(Maybe, the purge didn't work reliably and left some old libraries?)

> dpkg -l adb

Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
ii  adb            1:7.0.0+r1-1 amd64        Android Debug Bridge


> dpkg -l android-lib*

Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
ii  android-libadb 1:6.0.1+r55- amd64        Library for Android Debug
Bridge
ii  android-libbac 1:7.0.0+r1-1 amd64        Android backtrace library
ii  android-libbas 1:7.0.0+r1-1 amd64        Android base library
ii  android-libcut 1:7.0.0+r1-1 amd64        Android utils library for C
ii  android-libext 7.0.0+r1-2   amd64        Android ext4 utility library
ii  android-libf2f 7.0.0+r1-2   amd64        Android F2FS utility library
ii  android-liblog 1:7.0.0+r1-1 amd64        Android NDK logger interfaces
ii  android-libsel 7.0.0+r1-2   amd64        Security-Enhanced Linux for
Andro
ii  android-libspa 1:7.0.0+r1-1 amd64        Library for sparse files
ii  android-libunw 7.0.0+r1-3   amd64        libunwind for Android
ii  android-libuti 1:7.0.0+r1-1 amd64        Android Utility Function
Library
ii  android-libzip 1:7.0.0+r1-1 amd64        Library for ZIP archives


> My guess is that this change in the exit int of adb comes from upstream.
>  It seems appropriate for adb to exit with 1 in this case, no?

Yes it should exit with a 1 when there is a backtrace.

Thank You.
-- 
Senthil Kumaran S
http://www.stylesen.org/
http://www.sasenthilkumaran.com/