csgoGlow icon indicating copy to clipboard operation
csgoGlow copied to clipboard

Keeps turning off

Open useking opened this issue 6 years ago • 10 comments

Hack keeps turning off the my game crashes in a few seconds. I don't do anything with the terminal, i just leave it open and it keeps turning off after a few seconds.

useking avatar Sep 25 '18 06:09 useking

Any useful console output? Any errors given?

aKalisch avatar Sep 26 '18 14:09 aKalisch

nothing, csgo just crashes

useking avatar Sep 27 '18 08:09 useking

same, keeps crashing. plz fix

ghost avatar Oct 03 '18 15:10 ghost

It's Mojave; I suspect strongly the additional security Apple have applied is killing processes which display adverse behaviour (e.g. reading/writing other processes' memory) — disabling SIP (System Integrity Protection) makes no difference.

The hack itself is what dies, exit status 1, not the game for me. On repeated execution, there's often a momentary flash of outlines as the write succeeds prior to being killed. Adding printf school of tracing diagnostics, there is no particular point in execution where it is killed consistently. (Often early enough to not have any writes, just as often getting a few ticks of writes through.)

An executable binary compiled on High Sierra crashes on Mojave (at a random point, though usually quite quickly) and runs fine on High Sierra. (No difference if recompiled on Mojave.) Running from within Xcode (to try to catch exceptions/actual crashes and drop into a debugger) indicates no actual crash, just the 1 exit status code. (Running the process to debug as root is a build option; edit your Product→Scheme→Run→Debug Process As to indicate root.)

amcgregor avatar Oct 09 '18 03:10 amcgregor

could you simplify that i didnt get any of that

useking avatar Oct 10 '18 23:10 useking

@useking Alas, I can not. Instead of "Hack keeps turning off the my game crashes in a few seconds." I gave a full description of the problem environment, a clear attempt at diagnostics myself (printf school of debugging means adding print statements all over the place and watching the output to see exactly where it gets killed; which message is last, basically) and demonstrated a willingness to try variations to try to debug the problem. Basically, my comment was for iseekwonderful, not you? (If there can be a non-insulting way to say "that's not for you"…)

For now this boils down to: keep a copy of High Sierra around, it's more stable and "less secure" by allowing this type of cross-process modification or "hack". At least, until some other solution can be found which doesn't trigger protections.

amcgregor avatar Oct 12 '18 12:10 amcgregor

Won't even start to work! I used it a lot a few months back, but since Mojave I can't run the csGlow

phildental avatar Nov 21 '18 03:11 phildental

What amcgregor is trying to say is, Mojave kills the hack because it looks suspicious, so it doesn't work.

Just downgrade to High Sierra, but be VERY CAREFUL. Things will break, so be very very very very very careful, and back everything up so you don't lose your stuff.

PatheticMustan avatar Mar 09 '19 01:03 PatheticMustan

What amcgregor is trying to say is, Mojave kills the hack because it looks suspicious, so it doesn't work.

Just downgrade to High Sierra, but be VERY CAREFUL. Things will break, so be very very very very very careful, and back everything up so you don't lose your stuff.

I guess its not worth it then.

phildental avatar Mar 11 '19 12:03 phildental

Not worth it if you already have Mojave.

PatheticMustan avatar Mar 11 '19 18:03 PatheticMustan