Thank you, David, for posting my message here. I had found some tools that might be useful: sdk/android/qtools. Unfortunately, there is a lack of documentation on it. I was able to figure out that I can see when, for instance, console service is started/ended
$ out/host/linux-x86/bin/read_pid traces/emutrace ... t161329866 fork tgid 33 pid 33 t161356095 switch 33 t161452989 argc: 1 argv[0]: /system/bin/sh t161475182 name 33 t161482893 mmap 00008000 - 0001b000, offset 00000000 '' t161485265 mmap 0001b000 - 0001c000, offset 00013000 '' t161496358 mmap b0001000 - b0009000, offset 00001000 '' t161498814 mmap b0009000 - b000a000, offset 00009000 '' t161577659 munmap afd00000 - afd41000 t161580514 mmap afd00000 - afd41000, offset 00000000 '' t161584116 munmap afd41000 - afd44000 t161586119 mmap afd41000 - afd44000, offset 00041000 '' t161593931 munmap afd44000 - afd4f000 t161673708 exit 11 Perhaps, I might try to trace few more system calls (some kind of ptrace) using this approach? On Oct 6, 6:19 pm, David Turner <di...@android.com> wrote: > This is not related to the NDK, try android-porting instead. > > > > > > > > On Wed, Oct 5, 2011 at 2:51 AM, Dmitry <divis1...@gmail.com> wrote: > > Hi, > > > I'm trying to run custom Android build on emulator. > > This build is created for Cortex-a9, so I had selected the -armv7 > > kernel image (from prebuilt/android-arm/kernel) and use -qemu -cpu > > cortex-a9 option. (I had cloned the latest external/qemu) > > Unfortunately (well, as expected), this configuration does not work. > > Kernel is starting, init process is started, init launches some > > services, but they are terminated after some time, and finally system > > halts. > > One more issue is that I cannot connect to the emulator with adb. > > (What is interesting, adbd is started by init but is not terminated. I > > can see emulator-5554, but it is offline). > > > I had turned off most of the services (including critical, like > > servicemanager) in a hope that I just too slow in connecting to > > emulator with adb. No luck. > > > I'm suspecting that cortex-a9 emulation is a problem and would like to > > debug it, but do not know how to do this. I can debug the kernel > > itself (using qemu -s -S debugging), but this seems to me not optimal > > (mostly because I do not know the kernel so good). > > > I know that logcat can produce the crash stack of user-space > > application. Since I do not have adb, I do not have this stack. It > > seems that bionic intercepts aborting signals and directs the output > > to debuggerd (which is also crashing in my emulator setup). > > > Any guess are welcome. > > P.S. Not sure this is correct group for this discussion... > > > Dmitry > > > -- > > You received this message because you are subscribed to the Google Groups > > "android-ndk" group. > > To post to this group, send email to android-...@googlegroups.com. > > To unsubscribe from this group, send email to > > android-ndk+unsubscr...@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/android-ndk?hl=en. -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
