WorksButNotTested

Even more minimal reproducer: ```js Stalker.trustThreshold = -1; Stalker.follow(Process.id,{}); new ModuleMap().values().forEach(m => { console.log(`Found: ${m.name}`); if (m.name.startsWith('libstdc++')) { console.log(`Excluding: ${m.name}`); Stalker.exclude(m); } }); ```

I believe it will be if you call ‘ gum_stalker_activate_experimental_unwind_support’. Subject to any symbol resolution issues discussed in the PR.

Does it work if you use the gum_stalker_exclude API? The stalker type is supposed to be opaque I think. If the structure packing and alignment aren’t matched exactly then you...

The test [here](https://github.com/frida/frida-gum/blob/e44f6758e483d4ef42bd48f99b126d5b28a3cf50/gum/arch-arm/gumarmwriter.c#L631) should simply be omitted.

Seems the issue is cause by capstone interpreting this instruction as having a fourth immediate operand which is implicitly an LSL shift value. Rather than having 3 operands with the...

The output instructions will be, this keeps the logic simple and maintains the approach of the other shifted operations which calculate the shifted value first before adding the PC: ```c...

Sounds like your issue is that the binaries are built for Ubuntu 20.04, but you’re running on Ubuntu 18.04. OS suggest you try following the instructions for compiling from source....

In order for the 20.04 chroot to work, you will need to make sure it bind mounts the /proc file system. Also the Frida tools and target will need to...

This doesn't appear to cause any issues with ARM stalker in the tests, but nonetheless is incorrect and has therefore been fixed.

The defect is [here](https://github.com/frida/frida-gum/blob/e44f6758e483d4ef42bd48f99b126d5b28a3cf50/gum/arch-arm/gumarmrelocator.c#L579). code should read: ```c gum_arm_writer_put_add_reg_reg_reg (ctx->output, target, target, right->reg) ```