-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
libcgo.so contains writable and executable sections #1246
Labels
Comments
This #if directive, which I have found needs to be added at the end of the .S files I listed above, marks the stack region to be non-executable, so that if someone tries to execute machine code in the stack region of memory it will cause an exception. Without it, for assembly code, gcc assumes that it is ok for the stack to be executable. Does Go ever need to execute machine code that is directly stored in the stack region? For more info on this, you might want to take a look at the article on wikipedia about "Executable space protection". What do you think? Do you need more information? Can you please consider adding this if Go does not need the stack to be executable? Thanks much, William |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by w.d.hubbs:
The text was updated successfully, but these errors were encountered: