Try starce-ing "init" itself, but make sure "-f" and "-F" flags are passed as arguments to follow child processes (as well as vforks) as and when they get forked. For the v-0.9 sdk of Android, init.rc acts more like an input to the "init" and I guess you cannot add a new command in init.rc and expect it to wok as though it is invoked from the shell prompt. As far as I understand, only the Android "init" process can interpret the make use of the init.rc in v-0.9 sdk of Android.
Warm Regards, Anil On Thu, Oct 2, 2008 at 10:37 PM, twebb <[EMAIL PROTECTED]> wrote: > > I'm trying to use strace (from benno > http://benno.id.au/blog/2007/11/18/android-runtime-strace) > to trace runtime and understand what happens at startup of android but > no luck. init.rc appears to have changed between m5 and 0.9 and there > is no longer a runtime, plus the mechanics of how processes are > started in init.rc is different. So I try to run strace on this line > in init.rc and get no results. > > strace -ff -F -tt -s 200 -o /data/local/tmp \ > service zygote /system/bin/app_process -Xzygote /system/bin --zygote -- > start-system-server > > Can anyone offer some suggestions for strace'ing android 0.9 startup? > > Thanks, > twebb > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---
