Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed injections are still tracked and will cause a crash when they are "ejected" #12

Closed
RobotsOnDrugs opened this issue Mar 10, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@RobotsOnDrugs
Copy link
Owner

Triggered by Iperius Remote which uses a 64-bit process and a 32-bit process with the same name.

[2024-03-09 18:22:21.186] [WARN] Could not inject into IperiusRemote.exe (PID 9244): mismatch between target and payload architecture
[2024-03-09 18:22:21.211] [INFO] Hooked existing process AweSun.exe (PID 3368)
[2024-03-09 18:22:37.169] [INFO] Shutting down...
[2024-03-09 18:22:37.173] [INFO] Trace NoBlockInput was successfully terminated.
thread 'ctrl-c' panicked at .cargo\registry\src\index.crates.io-6f17d22bba15001f\dll-syringe-0.15.2\src\syringe.rs:225:9:
ejected module survived
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
@RobotsOnDrugs
Copy link
Owner Author

Fixed in 0.7.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant