Backtracing Async functions (+Task return type)

vfsfitvnm / frida-il2cpp-bridge

A Frida module to dump, trace or hijack any Il2Cpp application at runtime, without needing the global-metadata.dat file.

https://github.com/vfsfitvnm/frida-il2cpp-bridge/wiki

MIT License

974 stars 199 forks source link

Backtracing Async functions (+Task return type) #535

Open HomerSimpson00007 opened 1 month ago

HomerSimpson00007 commented 1 month ago

Was using the Backtracer (Works very well!), But entountered a problem, when trying to trace an async function, the backtrace result is always the same, all functions originate from MoveNext function (Due to the Statemachine), example: 0x06301eb8+0x000 TBetterBinaryProtocol::WriteBinaryAsync 0x062ccf98+0x094 Thrift.Protocol.TProtocol.<WriteStringAsync>d__39::MoveNext

Any other idea to backtrace such functions?

commonuserlol commented 1 month ago

it's good idea to share your code. I guess you need backtrace the WriteStringAsync function, or use tracer on target class(es)

vfsfitvnm commented 2 weeks ago

Any other idea to backtrace such functions?

No clue!