-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
doc(debug): add why breakpoints may fail and clean up manual configuration #6893
doc(debug): add why breakpoints may fail and clean up manual configuration #6893
Conversation
What do you think about adding IDE specific instructions (since I'd imagine nearly all users of debug are using one of the IDEs unless they are....adventurous). Some JB specific things I can think of:
I don't recall what we found with regards to |
b565609
to
58493ee
Compare
PTAL @etanshaul |
Include note for `cannot find debugger path` errors.
Codecov Report
@@ Coverage Diff @@
## main #6893 +/- ##
==========================================
- Coverage 70.48% 68.83% -1.65%
==========================================
Files 515 551 +36
Lines 23150 25301 +2151
==========================================
+ Hits 16317 17416 +1099
- Misses 5776 6712 +936
- Partials 1057 1173 +116
Continue to review full report at Codecov.
|
corresponding language plugin to be installed. If it is not installed, | ||
the debugger will not attach and breakpoints will not be hit. | ||
|
||
**Breakpoints on startup path are not hit.** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean by startup path here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant the container execution initialization path (e.g., from main() to listening)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Retitled: let me know if that's still unclear.
If this mapping is incorrect, then the remote debugging runtime | ||
will not be able to find the source file for the breakpoint. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way to manually fix this mapping ? any pointers on how users can look into this setting and where it is configured.
intended for deployment. In these cases, the source mapping must | ||
use the build-time paths. For example, many Go builds use a `golang` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah looks like you have documented resolution here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add more details around how to fix it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cloud Code generally prompts in these situations. It really is IDE-by-IDE
@quoctruong, @etanshaul: should we add anything else here for Go, like
-trimpath
?