-
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
go binary compiled for debug crashes and removed because of wrong codesign #69212
Comments
Maybe #63997 ? |
I thought about that as well, bu the problem here isn't that a preinstalled binary like
Thanks |
does it work if you set CC to the system clang? |
I'm not sure how to do that.
Or :
That said, if I put an intentional typo :
So I'm confused |
It's worth noting, I guess, that I keep working on the code, trying to do stuff without debugging, and sometimes the code has something different that now it accepts to run in debug. |
I set CC to the system clang, but it doesn't work, still can't debug |
I have no problems anymore, and not sure how I fixed it. |
Go version
go version go1.23.0 darwin/arm64
Output of
go env
in your module/workspace:What did you do?
Compiled binary with
-l
to be run in debug, this is the command line used by vscodeWhat did you see happen?
Run the produced binary :
Then the binary is removed from disk.
What did you expect to see?
Correct execution.
In the console log, macOS show the following :
Here is the
codesign
output for the binary :If I re-sign the binary it runs :
Codesign info for the re-signed binary :
The text was updated successfully, but these errors were encountered: