That's another story, but I agree.  Usually temporal logic properties
would want to talk about higher level things: such as method call /
return sequences (after a thread accesses the internet it never writes
any data to a persistent sink).

Kris

On Thu, May 9, 2013 at 8:44 AM, Julian Schütte <julian.schue...@gmx.net> wrote:
> You probably do not want to alter the Android sources but rather the
> application to monitor. Tracing registers at bytecode level is possible when
> injecting tracing code into the applications byte code. Have a look at the
> apkil tool to get started. However, I doubt that evaluating temporal logic
> over registers will get you very far, when dealing with arrays, return
> values etc.
> Best regards,
> Julian
>
>
>
> Emeric VIGIER <emeric.vig...@gmail.com> schrieb:
>
>
>>Read and store each register after each processor instruction? Are you
>>kidding? Can you imagine the overhead this could ever bring to the
>>normal
>>operation of the system?
>>
>>Emeric
>>Le 8 mai 2013 12:59, "Zhazira" <zhazko...@gmail.com> a écrit :
>>
>>> I'm currently doing my master thesis. And my task is dynamically
>>execute
>>> Android apps and monitor temporal Logic properties.
>>>
>>> What I want is to try to read all current register's values and their
>>tags
>>> after every instruction execution and write to logs. Is it possible
>>to
>>> change source code of Android? If so can you please give directions
>>in
>>> which part of source code I should focus or how I can do it. I'm new
>>in
>>> this topic and I already tried to look at Android source code, but
>>not able
>>> to find out which part is responsible or handles each instruction
>>execution.
>>>
>>> Please, could you help me with this? I would very much appreciate
>>your
>>> help.
>>>
>>> --
>>> --
>>> unsubscribe: android-kernel+unsubscr...@googlegroups.com
>>> website: http://groups.google.com/group/android-kernel
>>> ---
>>> You received this message because you are subscribed to the Google
>>Groups
>>> "Android Linux Kernel Development" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>send an
>>> email to android-kernel+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>>--
>>--
>>unsubscribe: android-kernel+unsubscr...@googlegroups.com
>>website: http://groups.google.com/group/android-kernel
>>---
>>You received this message because you are subscribed to the Google
>>Groups "Android Linux Kernel Development" group.
>>To unsubscribe from this group and stop receiving emails from it, send
>>an email to android-kernel+unsubscr...@googlegroups.com.
>>For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
>
> --
> --
> unsubscribe: android-kernel+unsubscr...@googlegroups.com
> website: http://groups.google.com/group/android-kernel
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Linux Kernel Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-kernel+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
-- 
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
--- 
You received this message because you are subscribed to the Google Groups 
"Android Linux Kernel Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-kernel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to