-
-
Notifications
You must be signed in to change notification settings - Fork 353
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
Executable stops working #130
Comments
I have the same issue you faced if you find ways to fix it. Can you post the solution here? Thanks in advance. |
Perhaps you fail to run because you are running the binary in different machine. Example: shc -r -f script.sh -o script |
Hi, |
I had the same problem on Arch linux. Adding "-r" switch worked for me. No idea why this works. The manual text talks about "relaxing security". The "-r" switch seems to be an undocumented mandatory switch to get expected behaviour. See my similar report here: #151 (comment) |
Hello, can you explain why the executable suddenly stops working and produces random characters?
This is the output of the executable that is failing
user>./error_run_healthcheck_prak.x
./error_run_healthcheck_prak.x: ▒▒▒)▒▒▒+▒d▒▒▒U2▒v▒▒b▒p▒
This is the output of the executable that is working
hdfsuser@cdrl-hd-en4-~/covid19>./run_healthcheck_prak.x
Password:
The source script is the same, and at some point even the failing executable was working fine.
The text was updated successfully, but these errors were encountered: