Sysprogs forums › Forums › VisualGDB › VisualGD and Android-x86 on VirtualBox
- This topic has 5 replies, 3 voices, and was last updated 11 years, 9 months ago by support.
-
AuthorPosts
-
August 17, 2012 at 11:12 #524AnonymousParticipant
Hi All,
I tried debug app on android-x86 runned in the Virtual Box but received next message
“Cannot query process list”
with adblog:
D:ProjectsAndroid-sdksplatform-toolsadb.exe devices
List of devices attached
12.12.19.98:5555 device
Command exited with code 0
D:ProjectsAndroid-sdksplatform-toolsadb.exe -s 12.12.19.98:5555 shell ps
PID USER VSZ STAT COMMAND
1 0 424 S /init
2 0 0 SW [kthreadd]
3 0 0 SW [ksoftirqd/0]
5 0 0 SW [kworker/u:0]
6 0 0 SW [migration/0]
7 0 0 SW [migration/1]
8 0 0 SW [kworker/1:0]
9 0 0 SW [ksoftirqd/1]
10 0 0 SW [kworker/0:1]
11 0 0 SW [migration/2]
13 0 0 SW [ksoftirqd/2]
14 0 0 SW [migration/3]
16 0 0 SW [ksoftirqd/3]
17 0 0 SW< [khelper]
23 0 0 SW< [suspend]
199 0 0 SW [sync_supers]
201 0 0 SW [bdi-default]
203 0 0 SW< [kblockd]
251 0 0 SW< [ata_sff]
261 0 0 SW [khubd]
406 0 0 SW [kswapd0]
408 0 0 SW [fsnotify_mark]
410 0 0 SW< [crypto]
971 0 0 SW [kworker/3:1]
1042 0 0 SW [scsi_eh_0]
1045 0 0 SW [scsi_eh_1]
1048 0 0 SW [kworker/u:3]
1051 0 0 SW [kworker/2:1]
1065 0 0 SW [kworker/0:2]
1118 0 0 SW< [binder]
1140 0 2640 S /bin/sh
1145 0 2640 S /bin/sh
1149 0 0 SW [kworker/3:2]
1150 0 0 SW [kworker/1:2]
1152 0 0 SW [kworker/2:2]
1164 0 0 SW [kjournald]
1226 0 0 SW< [kpsmoused]
1242 0 0 SW< [krfcommd]
1280 0 1908 S /sbin/v86d
1291 0 0 SW [flush-8:0]
1299 0 368 S /sbin/ueventd
1304 1000 1096 S /system/bin/servicemanager
1305 0 5016 S /system/bin/vold
1306 0 7580 S /system/bin/netd
1307 0 960 S /system/bin/debuggerd
1308 1001 11600 S /system/bin/rild
1309 0 584m S zygote /bin/app_process -Xzygote /system/bin –zygote
1310 1019 10464 S /system/bin/drmserver
1311 1013 43732 S /system/bin/mediaserver
1312 1002 2008 S /system/bin/dbus-daemon –system –nofork
1313 0 1160 S /system/bin/installd
1314 1017 2648 S /system/bin/keystore /data/misc/keystore
1315 0 1132 S /system/bin/powerbtnd
1317 0 1152 S /system/bin/sh
1318 0 1032 S /system/bin/logcat -v time -f /data/log.txt
1319 0 4576 S /sbin/adbd
1328 0 0 SW< [loop0]
1356 1000 694m S system_server
1431 1000 601m S com.android.systemui
1567 10006 617m S com.google.process.gapps
1597 10028 592m S com.android.inputmethod.latin
1613 1001 609m S com.android.phone
1625 10053 618m S com.android.launcher
1677 10008 634m S android.process.acore
2059 10068 1032 S logcat -v brief
2072 10025 614m S com.android.vending
2120 1014 1272 S /system/bin/dhcpcd -o domain_name_servers -ABKL -h an
2277 10029 590m S com.android.defcontainer
2305 10026 590m S com.android.musicfx
2322 10032 605m S com.keramidas.TitaniumBackup
2378 10064 591m S com.google.android.partnersetup
2390 10075 590m S com.svox.pico
2403 10044 593m S com.google.android.googlequicksearchbox
2416 10062 593m S com.android.quicksearchbox
2592 1000 606m S com.android.settings
2676 10098 619m S org.libsdl.app
2712 10033 602m S com.google.android.gm
2731 10006 595m S com.google.android.gsf.login
2761 10068 597m S com.antivirus
2779 10058 593m S android.process.media
2800 10068 976 S logcat -v brief
2806 0 1136 S /system/bin/sh -c ps
2808 0 2640 R ps
Command exited with code 0Is it possible ?
Thanks!
August 17, 2012 at 20:09 #2272supportKeymasterWhich version of Android are you using and what exact device? It looks like the output of the ps command looks differently from the usual one.
August 21, 2012 at 04:20 #2273AnonymousParticipantThank you for your Reply!
I tried use android-x86-4.0-eth0-gen_x86-20120726.iso from tabletsx86 org as test device.
Of course, this is a port Android 4.0 on x86 platform with arm support.
As test device, it work great, but debugger can’t find it. As I understand, this happen because ps output
format not the same as emulator ps and visualgdb parser can’t find req. information…So, walk under debugger on it – impossible…
Thanks.
January 27, 2013 at 19:21 #2275derodoParticipantSame here. Trying to debug a sample app on Galaxy S gives this same behevior. Any hints?
“Cannot query process list”
D:android-sdksdkplatform-toolsadb.exe devices
List of devices attached
33322AFABF1300EC device
Command exited with code 0
D:android-sdksdkplatform-toolsadb.exe -s 33322AFABF1300EC shell ps
PID USER VSZ STAT COMMAND
1 root 476 S /init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [watchdog/0]
5 root 0 SW [events/0]
6 root 0 SW [khelper]
7 root 0 SW [async/mgr]
8 root 0 SW [suspend]
9 root 0 SW [sync_system_wor]
10 root 0 SW [sync_supers]
11 root 0 SW [bdi-default]
12 root 0 SW [kblockd/0]
13 root 0 SW [kseriod]
14 root 0 SW [kmmcd]
15 root 0 SW [kondemand/0]
16 root 0 SW [pet_watchdog/0]
17 root 0 SW [khungtaskd]
18 root 0 SW [kswapd0]
19 root 0 SW [crypto/0]
37 root 0 SW [kapmd]
38 root 0 SW [pvr_timer/0]
39 root 0 SW [vsync_workqueue]
40 root 0 SW [sec_jack_wq]
41 root 0 SW [irq/38-sec_head]
42 root 0 SW [irq/167-fsa9480]
43 root 0 SW [svnetd/0]
44 root 0 SW [spi_gpio.3]
51 root 0 SW [file-storage]
52 root 0 SW [irq/34-proximit]
53 root 0 SW [gp2a_wq]
55 root 0 SW [kstriped]
56 root 0 SW [kconservative/0]
57 root 0 SW [binder]
58 root 0 SW [l2cap]
59 root 0 SW< [krfcommd]
60 root 0 SW [irq/334-melfas_]
61 root 0 SW [melfas_touchkey]
62 root 0 SW [qt602240_wq]
63 root 0 SW [mmcqd]
64 root 0 SW [irq/308-qt60224]
65 root 0 SW [max8998-charger]
66 root 0 SW [irq/39-max8998-]
67 root 0 SW [mmcqd]
68 root 376 S /sbin/ueventd
69 root 0 SW [Si4709_wq]
70 root 0 SW [TouchSense Play]
85 shell 760 S /system/bin/sh
88 system 832 S /system/bin/servicemanager
89 root 6024 S /system/bin/vold
90 system 1936 S /system/bin/notified_event
91 root 3884 S /system/bin/netd
92 root 708 S /system/bin/debuggerd
93 radio 9604 S /system/bin/rild
94 system 1044 S /system/bin/npsmobex
95 system 7972 S /system/bin/drexe
96 root 125m S zygote /bin/app_process -Xzygote /system/bin –zygot
97 media 38100 S < /system/bin/mediaserver
98 bluetoot 1280 S /system/bin/dbus-daemon –system –nofork
99 root 840 S /system/bin/installd
105 keystore 1768 S /system/bin/keystore /data/misc/keystore
107 compass 2880 S /system/bin/orientationd
108 compass 844 S /system/bin/geomagneticd
110 gps 16464 S /system/vendor/bin/gpsd -c /system/vendor/etc/gps.xm
112 system 13968 S /system/bin/tvoutserver
113 root 3420 S /sbin/adbd
153 root 0 SW [pvr_workqueue]
173 shell 392 S /system/bin/immvibed
529 system 254m S system_server
607 root 0 SW [iscan_sysioc]
608 root 0 SW [dhcp_sysioc]
609 root 0 SW [dhd_watchdog]
610 root 0 SW [dhd_dpc]
611 root 0 SW [dhd_sysioc]
614 root 0 SW [irq/164-bcmsdh_]
621 wifi 2724 S /system/bin/wpa_supplicant -Dwext -ieth0 -c/data/wif
625 system 152m S com.android.systemui
633 app_7 141m S com.swype.android.inputmethod
637 radio 152m S com.android.phone
638 app_10 142m S android.process.media
639 bluetoot 134m S com.broadcom.bt.app.system
644 app_19 158m S com.sec.android.app.twlauncher
685 dhcp 880 S /system/bin/dhcpcd -ABK eth0
699 app_22 239m S com.google.process.gapps
760 app_19 178m S android.process.acore
1041 root 0 SW< [loop0]
1042 root 0 SW [kdmflush]
1054 root 0 SW [kcryptd_io]
1055 root 0 SW [kcryptd]
1131 root 0 SW< [loop1]
1132 root 0 SW [kdmflush]
1133 root 0 SW [kcryptd_io]
1134 root 0 SW [kcryptd]
1164 root 0 SW< [loop2]
1165 root 0 SW [kdmflush]
1166 root 0 SW [kcryptd_io]
1167 root 0 SW [kcryptd]
1241 root 0 SW< [loop3]
1242 root 0 SW [kdmflush]
1243 root 0 SW [kcryptd_io]
1244 root 0 SW [kcryptd]
1263 root 0 SW< [loop4]
1264 root 0 SW [kdmflush]
1265 root 0 SW [kcryptd_io]
1266 root 0 SW [kcryptd]
1272 root 0 SW< [loop5]
1273 root 0 SW [kdmflush]
1274 root 0 SW [kcryptd_io]
1275 root 0 SW [kcryptd]
1278 root 0 SW< [loop6]
1279 root 0 SW [kdmflush]
1280 root 0 SW [kcryptd_io]
1281 root 0 SW [kcryptd]
1282 root 0 SW< [loop7]
1283 root 0 SW [kdmflush]
1284 root 0 SW [kcryptd_io]
1285 root 0 SW [kcryptd]
1287 root 0 SW< [loop8]
1288 root 0 SW [kdmflush]
1289 root 0 SW [kcryptd_io]
1290 root 0 SW [kcryptd]
1291 root 0 SW< [loop9]
1292 root 0 SW [kdmflush]
1293 root 0 SW [kcryptd_io]
1294 root 0 SW [kcryptd]
1338 app_37 160m S com.google.android.apps.maps
2679 app_44 136m S com.android.providers.calendar
2718 system 137m S com.wssyncmldm
2795 root 0 SW [flush-179:0]
3053 app_25 134m S com.android.defcontainer
3063 app_16 134m S com.android.voicedialer
3073 app_17 134m S com.google.android.partnersetup
3082 app_38 134m S com.svox.pico
3089 system 134m S com.sec.android.app.controlpanel
3096 app_2 135m S com.noshufou.android.su
3115 app_9 134m S com.sec.android.app.samsungapps.una2
3117 system 135m S com.sec.android.providers.drm
3131 system 134m S com.android.MtpApplication
3151 app_37 159m S com.google.android.apps.maps:GoogleLocationService
3184 root 760 S /system/bin/sh -c logcat -v threadtime
3185 root 800 S logcat -v threadtime
3201 app_37 148m S com.google.android.apps.maps:FriendService
3221 app_37 150m S com.google.android.apps.maps:LocationFriendService
3375 root 0 SW [flush-138:10]
3428 system 134m S com.android.settings.mt
3645 root 760 S /system/bin/sh -c logcat -v long
3646 root 1224 S logcat -v long
3792 app_13 134m S com.sec.android.app.unifiedinbox
3799 app_65 168m S com.android.vending
3828 app_22 141m S com.google.android.gms
3843 root 760 S /system/bin/sh -c ps
3844 root 1652 S /sbin/ext/busybox sh /sbin/ps
3849 root 1652 R /sbin/ext/busybox /sbin/ps
Command exited with code 0January 28, 2013 at 11:16 #2274supportKeymasterHi,
Yes, the bug is caused by the ‘ps’ command producing slightly different output from the one on most of the Android devices.
We have fixed this in the upcoming VisualGDB 3.0 release. We are planning to release the beta (also supporting vs-android integration) at the end of this week.February 2, 2013 at 11:16 #2276supportKeymasterPlease try VisualGDB 3.0 Beta 1. The problem is fixed there.
-
AuthorPosts
- You must be logged in to reply to this topic.