This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Met Problem on Enable SystemTap on Android


Hi,

Not sure this is same use case but "adb shell cat xxx" or "adb shell xxx" performed on my host is expected to run the right thing on target.
For example, I could do "adb shell /data/systemtapxxx/bin/staprun /data/systemtapxxx/test.ko" and get ouput directly on my host (but I prefer dumping in a tmpfs then pull on host). This is silicon vendor dev platform and not phone.

I still have previous mail in my Inbox to have a look but this is not top of my list :-(


Regards
Fred

Frederic Turgis
OMAP Platform Business Unit - OMAP System Engineering - Platform Enablement



>
Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920

-----Original Message-----

>From: Josh Stone [mailto:jistone@redhat.com]
>Sent: Monday, September 26, 2011 10:52 PM
>To: Turgis, Frederic
>Cc: SystemTap
>Subject: Re: Met Problem on Enable SystemTap on Android
>
>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
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]