public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "$rik@nth " <srikanth007m@gmail.com>
To: Alexander Lochmann <alexander.lochmann@tu-dortmund.de>
Cc: William Cohen <wcohen@redhat.com>, systemtap@sourceware.org
Subject: Re: Fwd: Systemtap for Android
Date: Wed, 15 Jun 2016 02:48:00 -0000	[thread overview]
Message-ID: <CANKSX+Efa8wW8bT4fHvL3KgauhMzAJOrFbrN9cF=Og0oRFEgJw@mail.gmail.com> (raw)
In-Reply-To: <bbd7c4bf-3738-edb2-e179-6465bc3275ef@tu-dortmund.de>

On Tue, Jun 14, 2016 at 5:31 PM, Alexander Lochmann
<alexander.lochmann@tu-dortmund.de> wrote:
> On 06/09/2016 10:10, $rik@nth  wrote:
>> Thank you William for your pointers. Definitely i will go through them
>> to set a starting point.
> I already did that job. :)
> Have a look at my git repo: https://github.com/flipreverse/systemtap-android
Thank you Alexander. I will try it.
>
> Cheers,
> Alex
>>
>> On Tue, Jun 7, 2016 at 7:51 PM, William Cohen <wcohen@redhat.com> wrote:
>>> On 06/06/2016 10:57 PM, $rik@nth  wrote:
>>>> Hi All,
>>>>
>>>> I am pretty much interested in using systemtap. But it is not
>>>> available for Android. So i would like to port it for Android using
>>>> cross tool chain. Before going into the deep, i would like to know if
>>>> someone already did similar exercise? or some hacks where we can use
>>>> it directly by using cross toolchain.  If yes, please share your
>>>> inputs to save time.
>>>>
>>>> Thanks in advance.
>>>>
>>>
>>> Hi,
>>>
>>> There have been some people using SystemTap on embedded arm systems and they have used cross compilation some time ago:
>>>
>>> http://omappedia.org/wiki/Systemtap
>>> https://sourceware.org/systemtap/wiki/SystemtapOnFedoraArm
>>>
>>> You might use those as a starting point for work on android.
>>>
>>> -Will
>>
>>
>>
>
>
> --
> Technische Universität Dortmund
> Alexander Lochmann                PGP key: 0xBC3EF6FD
> Otto-Hahn-Str. 16                 phone:  +49.231.7556141
> D-44227 Dortmund                  fax:    +49.231.7556116
> http://ess.cs.tu-dortmund.de/Staff/al
>



-- 
Thanks & Regards,
M.Srikanth Kumar.

      reply	other threads:[~2016-06-15  2:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANKSX+HD=6tiHYa6WKsXziV2emgdP7aNHKPbmB1tcg4LS2jenQ@mail.gmail.com>
2016-06-07  2:57 ` $rik@nth 
2016-06-07 14:21   ` William Cohen
2016-06-09  8:10     ` $rik@nth 
2016-06-14 12:01       ` Alexander Lochmann
2016-06-15  2:48         ` $rik@nth  [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANKSX+Efa8wW8bT4fHvL3KgauhMzAJOrFbrN9cF=Og0oRFEgJw@mail.gmail.com' \
    --to=srikanth007m@gmail.com \
    --cc=alexander.lochmann@tu-dortmund.de \
    --cc=systemtap@sourceware.org \
    --cc=wcohen@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).