expend20

Hello, I tried to reproduce it on [frida-gum's example,](https://github.com/frida/frida-rust/blob/main/examples/gum/stalker/src/main.rs) and it... just worked. So, Frida actually supports C++ exceptions on Windows, at least on this minimalistic example. Attaching the reproducer....

You were right, in the reproducer if I call `stalker.exclude()` for every virtual address except the instrumented module, it stops working. I wonder why do we have both: [excluded ranges](https://github.com/AFLplusplus/LibAFL/blob/40269a578b9f8a7a6b6d7e014f6fbf1e186e7dcd/libafl_frida/src/executor.rs#L175)...

> therefore we can achieve more speed (?) Instrumentation phase is one time cost, so it potentially will lead to only faster startup, fuzzing speed is not going to be...

Meanwhile I can try if Frida's exeptor can be of help

> as long as I checked with frida_libpng the speed dropped from 33k/sec to 22k/sec if I removed stalker.exclude(). (on linux) so i'd say it's still meaningful for performance reason...

Sure, tried next: * 1.65.0 release * 1.65.0 debug * 1.68.0-nightly release * 1.68.0-nightly debug the result is visually the same 

I did, it was a git clone&checkout to new directory. It's just boring to watch 5 minute gif, so I built it before the record. Here is the log with...

I'd be happy to provide any additional info to help to resolve the issue.

hey @coderedart, sorry for being dormant a bit. There is actually a call stack in the first post, is it helpful? Here is your branch:  cargo run log ```...

Thanks, I updated it to `0e186efb7eff4f4bfcf8001117cadb6a57743221` ``` 0e186efb7eff4f4bfcf8001117cadb6a57743221 (HEAD -> glutin_winit, origin/glutin_winit) cranky lint d5bda4c4af9d8f6f3909f18c81b8d887efdbf0e7 add more logging. ignore vsync option if not supported c8a130e50dad1bb712faff6cc1fb324cace36402 update pure glow example to...