Remove runtime.Breakpoint call #1601
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull Request Overview
This PR removes the runtime.Breakpoint call from the debug package's Fail function. The change addresses an issue where runtime.Breakpoint() causes a SIGTRAP signal when no debugger is attached, making it unsuitable for general use.
- Commented out the runtime.Breakpoint() call in the Fail function
- Removed the unused "runtime" import
weswigham
approved these changes
Aug 19, 2025
|
At best we could set a build tag that would apply when starting a launch task... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I guess this is not similar enough to☹️
debugger;, doing it without a debugger attach just does SIGTRAP.