Frida 12.6 Released ∞release
After a flurry of fixes across all platforms over the last few weeks, I figured it was time to do another minor bump to call attention to this release.
One particular fix is worth mentioning specifically. There was a long- standing bug in our Android Java integration, where exception delivery would intermittently result in the process crashing with GetOatQuickMethodHeader() typically in the stack-trace. Shout-out to Jake Van Dyke and Giovanni Rocca for helping track this one down. This bug has been around for as long as ART has been supported, so this fix is worth celebrating. 🎉
Our V8 runtime is also a lot more stable, child-gating works better than ever before, Android device compatibility is much improved, etc.
So bottom line is that this is the most stable version of Frida ever released – and now is the time to make sure you’re running Frida 12.6.
Changes in 12.6.1
- The exception delivery fix in the Android Java integration introduced a performance bottleneck when running the VM in interpreter mode, e.g. through Java.deoptimizeEverything(). For example when running the Dropbox app from start to login screen, this would take ~94 seconds on a Pixel 3 running Android 9, and now takes ~6 seconds.
Changes in 12.6.2
- Android Java integration now supports more arm64 systems thanks to a fix contributed by Giovanni Rocca.
- Android Java integration once again supports being used by more than one script at a time.
Changes in 12.6.3
- Java.choose() is now working again on Android >= 8.1, thanks to a fix contributed by Eugene Kolo.
- Android Java integration unhooking is now working again. This also means hooks are properly reverted on script unload.
- Frida can now talk to old versions of Frida, from before the addition of per-script runtime selection.
Changes in 12.6.4
- Build system is back in business on all platforms.
Changes in 12.6.5
- Linux thread enumeration is now working properly on x86-64.
- Stalker finally handles restartable Linux syscalls.
Changes in 12.6.6
- Android Java integration is back in fully working condition on 32-bit ARM.
Changes in 12.6.7
- Latest Chimera iOS jailbreaks are now supported; confirmed working on 1.0.8.
- Linux injector handles target processes where the libc’s name is ambiguous, which is often an issue on Android.
Changes in 12.6.8
- ObjC.Object now provides $moduleName, useful for determining which module owns a given class. Kudos to David Weinstein for contributing this neat feature!
Changes in 12.6.9
- Latest unc0ver jailbreak is now fully supported.
- Early instrumentation logic has been improved to fully support iOS 12. Kudos to Francesco Tamagni for helping get these tricky changes across the finish-line.
- Enumeration of memory ranges is now more reliable on iOS 12, as memory ranges belonging to threads are now correctly cloaked.
- Cloaked memory ranges are now compacted, making lookups faster.
- Child gating is able to hold children for longer than 25 seconds. Previously these would get resumed automatically after that accidental timeout. This also affects early instrumentation on Android, as it is built on top of child gating.
- Swift bindings support RPC and have been moved to Swift 5.0, thanks to John Coates’ awesome contribution.
Changes in 12.6.10
- Enumeration of memory ranges is now reliable on all platforms. There was a long-standing bug when a removal ends up splitting an existing range.
Changes in 12.6.11
- Enumeration of applications includes icons on iOS >= 12, thanks to a nice fix by CodeColorist.
- Gadget was taught how to detect the executable and package name of Android apps, thanks to a neat contribution by gebing.
- Cloaking of memory ranges got a critical fix affecting Windows users.
Changes in 12.6.12
- The frida-inject tool now supports passing parameters to the script through -P/–parameters. Kudos to Eugene Kolo for contributing this neat feature.
- Child-gating no longer deadlocks when script unload blocks. Kudos to Ioannis Gasparis for helping track this one down.
- Child-gating is more reliable as Frida now allocates file-descriptors in a higher range to avoid them getting closed by applications calling dup2() during a fork()+exec(). This would typically happen on Android when an app called Runtime.exec(). Kudos to Ioannis Gasparis for helping track this one down.
- The painful Android NDK upgrade to r20 landed, thanks to a slew of awesome contributions by Muhammed Ziad.
- Error-handling was improved to avoid crashing in scenarios where we fail to initialize due to lack of permissions. Kudos to pancake for reporting.
- The native lockdown integration for iOS that had been sitting in a branch for a very long time was finally merged. It is unfinished and considered unstable API, but had to be merged due to a major refactoring that’s in progress.
- Stalker now allows unfollow() from the transform callback, instead of crashing the process like it used to. Kudos to Giovanni Rocca for helping fix this.
- Gadget’s Android package name detection logic was improved to handle one edge-case not previously accounted for. Kudos to xiaobaiyey for reporting and suggesting a fix.
- The Java.registerClass() API was improved to support specifying the super class, along with a slew of fixes for both that API and handling of arrays with generics. Big thanks to gebing for these awesome improvements.
Changes in 12.6.13
- Constructor/destructor functions in Agent and Gadget are now finally correctly ordered, and our libc shim’s memory allocator hacks could be dropped. Those fragile hacks broke in a new and colorful way with 32-bit ARM processes on Android due to a subtle change in the toolchain’s libgcc.
- Our libc shim now also handles __cxa_atexit() and atexit(), where the former is crucial to avoid leaks.
Changes in 12.6.14
- The Java.registerClass() API was improved to support user-defined constructors and fields, thanks to the awesome improvements contributed by gebing.
- Temporary files are now cleaned up on all platforms.
- Ctrl+C is handled by frida-server on Windows to support graceful shutdown without leaving temporary files behind.