Repository navigation
Add console.log on client side #8
Description
Without having to implicitly pass messages, this is important because most of the time you will not have access to the console of the target app.
as a workaround:
import frida
import sys
pid = int(sys.argv[1])
function_address = int(sys.argv[2], 16)
process = frida.attach(pid)
script = process.session.create_script("""
function print(x) {
send({type:"msg",msg:x});
}
print ("Hello World");
""" % function_address)
def on_message(message, data):
payload = message['payload']
try:
type = payload['type']
if type == 'msg':
print payload['msg']
except:
print(message)
pass
script.on('message', on_message)
script.load()
Activity
oleavr commentedon Feb 18, 2015
Very good point. On the "client" side (python in this case) the
message.typefield issendwhenever send() was used, anderrorin case of an unhandled exception. Perhaps a third type could be added, and bindings are expected to handle that one explicitly?radare commentedon Feb 19, 2015
that would be a good way to do that imho. usually "print" is just for showing some notes to help the user, if you want something more complex you can implement more machinery in the client side to handle other kind of messages
oleavr commentedon Feb 19, 2015
Agreed. So then either we change
console.log()to send this message, or introduceprint()in the global scope. I would argue the former is rather useless as it is now.oleavr commentedon Feb 28, 2015
Implemented by 5b1d82c, and now also supported by frida/frida-python@59107ba and frida/frida-qml@d6b2c46.
radare commentedon Mar 1, 2015
Cool! Thanks
android_buildfix: don't link pthread when building for android (frida#8)