-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[Deployment] failed to run compiled magefile: signal: killed. #2636
Comments
Hello! Thank you for filing an issue. If this is a bug report, please include relevant logs to help us debug the problem. Join slack 🤖 to connect and communicate with our developers. |
You should execute bootstrap.sh to ensure that mage is installed correctly. |
已经执行了 bootstrap.sh 脚本,也遇到类似问题。 macOS 15 (ARM) |
I have executed the bootstrap.sh script and encountered similar problems. macOS 15 (ARM) |
Could you provide a complete description of the entire process? |
I updated Go to the latest version (1.23.1 for my M1 Mac) and now mage is working as expected. I was previously using Go 1.22.1, and I recently upgraded my macOS to the latest version. I'm not positive if updating my Mac caused the mage command to break, but it's working again now. |
OpenIM Server Version
3.8.0
Operating System and CPU Architecture
macOS (ARM)
Deployment Method
Source Code Deployment
Issue Description and Steps to Reproduce
mage start
error message: failed to run compiled magefile: signal: killed.
Analysis of the Crash Log
This is a crash report for a macOS application. Here are the main findings and analysis:
Crash Time and Environment:
Occurrence: September 20, 2024, 10:16:41
Operating System: macOS 15.0 (24A335)
Hardware Model: MacBookPro18,3
Crashed Application:
Process Name: 4b321c6aefc97053b5d0457049f070e4b6b70e66
Parent Process: mage
Responsible Process: goland (suggesting it might be a program run within the GoLand IDE)
Crash Type:
Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
Termination Reason: CODESIGNING 2 Invalid Page
Crashed Thread:
Thread 0 crashed, involving operations in dyld (dynamic linker)
Key Issues:
Invalid Code Signature: The report shows "Code Signature Invalid" and "CODESIGNING 2 Invalid Page", indicating issues with the program's code signature.
Memory Access Error: EXC_BAD_ACCESS suggests the program attempted to access a memory address it wasn't allowed to.
Crash Stack:
The crash occurred within internal functions of dyld, specifically while processing load commands of a Mach-O file (macOS executable format).
Possible Causes:
Code Signing Issue: The program's code signature might be invalid or corrupted.
Dynamic Linker Problem: dyld encountered issues while loading or validating the program.
Potential Security Measure: The system may have forcibly terminated the program due to detected code signing issues.
Suggested Resolution Steps:
Check and re-sign the application.
Ensure all dependent libraries are correctly signed and compatible with the current macOS version.
If this is a development application, review compilation and linking settings to ensure compatibility with the target macOS version.
Screenshots Link
The text was updated successfully, but these errors were encountered: