Skip to content
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

net: programs are not linked with networking libraries on Solaris #10221

Closed
4ad opened this issue Mar 23, 2015 · 1 comment

Comments

Projects
None yet
4 participants
@4ad
Copy link
Member

commented Mar 23, 2015

Solaris programs are always dynamically linked. In general, they use dlopen(3c) and dlsym(3c) to find symbols on demand. However, some tools like DTrace are not happy about it; you can't put a probe on, say, pid$target:libsocket.so:sendfile:entry because libsocket.so is not loaded yet when DTrace is setting up probes.

@4ad 4ad added the os-solaris label Mar 23, 2015

@4ad 4ad self-assigned this Mar 23, 2015

@rsc rsc removed the os-solaris label Apr 10, 2015

@rsc rsc added this to the Unplanned milestone Apr 10, 2015

@rsc rsc added the OS-Solaris label Apr 15, 2015

@gopherbot

This comment has been minimized.

Copy link

commented Apr 25, 2015

CL https://golang.org/cl/7941 mentions this issue.

@4ad 4ad closed this in b0e71f4 May 6, 2015

@mikioh mikioh modified the milestones: Go1.5, Unplanned May 6, 2015

@golang golang locked and limited conversation to collaborators Jun 25, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.