can't connect to ADB server

[李斌]

Hi all,
I want to do some experiments on Leakalizer(s2eandroid branch) and have some troubles.

------------------------------------------------------------
libin@libin-desk:~/myfile3/s2eandroid/build$  ./android-release/objs-nos2e/emulator -no-snapshot-load -no-snapshot-save -noskin -sysdir $LEAKALIZER/android-images/ledroid.avd/system -datadir $LEAKALIZER/android-images/ledroid.avd -kernel $LEAKALIZER/android-images/ledroid.avd/system/zImage -data $LEAKALIZER/android-images/ledroid.avd/userdata.img -snapstorage $LEAKALIZER/android-images/ledroid.avd/hda.img -sdcard $LEAKALIZER/android-images/ledroid.avd/sdcard.img -memory 256 -show-kernel -verbose -qemu -monitor stdio
emulator: autoconfig: -image (null)
emulator: autoconfig: -ramdisk /home/libin/myfile3/s2eandroid/android-images/ledroid.avd/system/ramdisk.img
emulator: Could not open file: : No such file or directory
emulator: Coult not find CPU ABI in build properties!
emulator: Default target architecture=arm
emulator: Could not open file: : No such file or directory
emulator: Could not find target API level / SDK version in build properties!
emulator: Default target API level: 1000
emulator: using core hw config path: /home/libin/myfile3/s2eandroid/android-images/ledroid.avd/system/hardware-qemu.ini
emulator: autoconfig: -skindir (null)
emulator: keyset loaded from: /home/libin/.android/default.keyset
emulator: found magic skin width=320 height=480 bpp=16

emulator: autoconfig: -ramdisk /home/libin/myfile3/s2eandroid/android-images/ledroid.avd/system/ramdisk.img
emulator: Using initial system image: /home/libin/myfile3/s2eandroid/android-images/ledroid.avd/system/system.img
emulator: WARNING: system partition size adjusted to match image file (169 MB > 66 MB)

emulator: autoconfig: -initdata (null)
emulator: Physical RAM size: 256MB

QEMU options list:
emulator: argv[00] = "./android-release/objs-nos2e/emulator"
emulator: argv[01] = "-show-kernel"
emulator: argv[02] = "-monitor"
emulator: argv[03] = "stdio"
emulator: argv[04] = "-android-hw"
emulator: argv[05] = "/home/libin/myfile3/s2eandroid/android-images/ledroid.avd/system/hardware-qemu.ini"
Concatenated QEMU options:
 ./android-release/objs-nos2e/emulator -show-kernel -monitor stdio -android-hw /home/libin/myfile3/s2eandroid/android-images/ledroid.avd/system/hardware-qemu.ini
emulator: registered 'boot-properties' qemud service
emulator: nand_add_dev: system,size=0xa900000,initfile=/home/libin/myfile3/s2eandroid/android-images/ledroid.avd/system/system.img
emulator: mapping 'system' NAND image to /tmp/android/emulator-jyZdCq
emulator: rounding devsize up to a full eraseunit, now a920000

emulator: nand_add_dev: userdata,size=0x4200000,file=/home/libin/myfile3/s2eandroid/android-images/ledroid.avd/userdata.img
emulator: registered 'boot-properties' qemud service
emulator: Adding boot property: 'dalvik.vm.heapsize' = '48m'
emulator: Adding boot property: 'qemu.sf.lcd_density' = '160'
emulator: nand_add_dev: cache,size=0x4200000
emulator: mapping 'cache' NAND image to /tmp/android/emulator-f35B2G
emulator: Kernel parameters: qemu=1 console=ttyS0 android.qemud=ttyS1 android.checkjni=1 ndns=1
emulator: Trace file name is not set

serial0 console
emulator: control console listening on port 5554, ADB on port 5555
emulator: can't connect to ADB server: Connection refused
emulator: ping program: /home/libin/myfile3/s2eandroid/build/android-release/objs-nos2e/ddms
QEMU 0.10.50 monitor - type 'help' for more information
(qemu-android) Uncompressing Linux...Uncompressing Linux...

ran out of input data

 -- System haltedemulator: User-config was not changed.
--------------------------------------------------------------------------------
Please tell me what is causing this problem. Why is emulator not
working in my case? Is there any solution?


Any help is greatly appreciated.
Thanks.
-- 
Bin Li

[AKA]

Hm... Two things that come to my mind:

* Make sure that you have installed the Android SDK... ADB should work from the terminal just by typing 'adb'.
* Double check if all the specified paths contain the required files (e.g. ramdisk.img and system.img).

cheers,
Andy

[AKA]

[JiangCat]

Hi, Andreas and Bin Li,

I have compiled the LeakAlizer, but I met some problems as follow:

1. After compiled the LeakAlizer, I checked the $LEAKALIZER/build/stp/bin, but I couldn't find the stp executable file, Is it normal right?

2. I cannot find the android image file 'ledroid.avd' which contains the leakalizer plugin extension as you all mentioned. So, could you please send me one copy of the file??

Great thanks.

B. Zhang

在 2012年4月9日星期一UTC+8上午9时51分53秒，李斌写道：

[Andreas Kichner]

Hi Bin Zhang.
It's been a while I have built Leakalizer. I try to answer your questions as best as possible:

(1) I can't really remember if one should see binaries in build/stp.
(2) You need to use the special-made image ledroid.avd that you can download here:
http://www.fragtsich.eu/leakalizer/ledroid.avd.zip
(3) I've found the files you were talking about:
http://www.fragtsich.eu/leakalizer/System.map
http://www.fragtsich.eu/leakalizer/prelink-linux-arm.map

If you have any new insights, please document them on the Leakalizer wiki page and/or in the docs/Leakalizer folder.
I think the main branch of S2E evolved quite a bit in the meantime - also the Android OS evolved from 2.3 to 4.4. Feel free to contribute code.

Best regards,
Andy