-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
plugin: test fails for debug sections on Darwin #27502
Comments
Change https://golang.org/cl/133435 mentions this issue: |
For some reason on darwin the linker still can't add debug sections to plugins. Executables importing "plugin" do have them, however. Because of issue 25841, plugins on darwin would likely have bad debug info anyway so, for now, this isn't a great loss. This disables the check for debug sections in plugins for darwin only. Updates #27502 Change-Id: Ib8f62dac1e485006b0c2b3ba04f86d733db5ee9a Reviewed-on: https://go-review.googlesource.com/133435 Reviewed-by: Brad Fitzpatrick <[email protected]>
I can't debug plugin on mac even in Go 1.13. Is there any progress? |
@juhwany As far as I know nobody is working on this. Sorry. |
It's really hard to code plugin without supporting debugging. Hope next Go release will fix this. |
It remains true that as far as I know nobody is working on this. This issue is marked "help wanted" and I hope that someone can help here. |
Change https://golang.org/cl/182959 mentions this issue: |
The other impediment to debugging plugins on macOS is #25841, I don't know if it has been fixed in the meantime (I suspect it hasn't). |
Change https://golang.org/cl/206198 mentions this issue: |
Assorted fixups in the linker needed to enable turning back on DWARF generation when building plugins for Darwin. Includes: - don't suppress import of runtime/cgo in the linker for Darwin if we are linking in plugin mode - in calcCompUnitRanges handle the case where we encounter linker-generated functions that have no associated Unit (and also have no DWARF) - generalize a guard in relocsym() include so as to avoid triggering a spurious error on go.info symbols in plugin mode Updates #21647. Updates #27502. Change-Id: I317fea97bef2f3461e31498e63f9fd6d8b8f4b23 Reviewed-on: https://go-review.googlesource.com/c/go/+/182959 Run-TryBot: Than McIntosh <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Cherry Zhang <[email protected]> Reviewed-by: Emmanuel Odeke <[email protected]>
Please answer these questions before submitting your issue. Thanks!
What did you do?
Rebuild the lastest tip version with all.bash
What did you expect to see?
All tests pass.
What did you see instead?
Does this issue reproduce with the latest release (go1.11)?
N/A
System details
The text was updated successfully, but these errors were encountered: