Re: Met Problem on Enable SystemTap on Android

[Josh Stone <jistone at redhat dot com>]

On 09/01/2011 01:44 AM, Turgis, Frederic wrote:
>> BTW, if you happen to have ssh listening on the target, then
>> you may be able to use "--remote $TARGET" to automate the
>> copy and staprun.  I'm considering adding a new remote
>> scheme, perhaps "--remote adb:..." to let you do this over
>> the Android debugging channel too.
> We don't have ssh listening by default so an adb scheme would be welcomed.

In case you missed it, I opened a bug for this with a prototype:
http://sourceware.org/bugzilla/show_bug.cgi?id=13194

As noted, I had issues trying to test it -- but I've played around with
a few other commands, and even a simple "adb shell cat" doesn't work.
It appears that adb doesn't pass along stdin when running a remote
command.  Only for the interactive "adb shell" does it fork and read
stdin to pass to the remote.  Since we need two-way communication for
stap, we might have to kludge a two-part solution, spawn an interactive
"adb shell" followed by writing "exec stapsh" to its stdin.

Now that I write that, it doesn't seem so hard, but I haven't had time
to play with it more.  If you're able to try my prototype and enhance it
to actually work, that would be great. :)

Thanks,
Josh