Skip to content

syscall: Syscall breaks when https request has been sent before (after upgrading to OS X Mavericks) #6649

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.

Sign up for GitHub

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

Jump to bottom
Closed
gopherbot opened this issue Oct 23, 2013 · 6 comments
Closed

syscall: Syscall breaks when https request has been sent before (after upgrading to OS X Mavericks) #6649

gopherbot opened this issue Oct 23, 2013 · 6 comments
Labels
FrozenDueToAge

Comments

@gopherbot
Copy link
Contributor

by tobstarr:

After upgrading to OS X Mavericks (10.9) I am running into this issue:

Somehow a syscall triggering an ssh connection is killed (and the mssage 'signal:
killed' is printed) if I am doing a https request before that system call. All works
fine if I do a plain http request:

Here is a script with which I can reproduce the issue (also attached)

https://gist.github.com/tobstarr/7122370

I tested it with go 1.1.2 but also with tip (go version devel +f257b02e7ffe Wed Oct 23
10:28:28 2013 -0400 darwin/amd64)

Everything was fine with OS X 10.8.

Attachments:

  1. test.go (355 bytes)
@rsc
Copy link
Contributor

rsc commented Oct 23, 2013

Comment 1:

https uses cgo to get the root CA set. but http uses cgo to translate
www.apple.com so it's not cgo specifically that's the problem.
On earlier versions of OS X, syscall.Exec was disallowed if the program had
created any threads. Nearly all Go programs create threads very early on,
so syscall.Exec almost always failed on OS X. Perhaps now instead of
returning an error it kills the program. Either way, I think you'd be
better off using os/exec to start and wait for a subprocess.

@gopherbot
Copy link
Contributor Author

Comment 2 by tobstarr:

The only reason I am using the syscall is that I want to "attach" to that ssh connection
but I can probably just hook my os streams in. I will give it a try. Still an odd issue.
Thanx!

@rsc
Copy link
Contributor

rsc commented Nov 27, 2013

Comment 3:

Labels changed: added go1.3maybe.

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 5:

Labels changed: added release-none, removed go1.3maybe.

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 6:

Labels changed: added repo-main.

@davecheney
Copy link
Contributor

Comment 7:

Based on the conversation in this issue I am tentatively marking it as fixed. Please
feel free to comment if you feel this is in error.

Status changed to Fixed.

@golang golang locked and limited conversation to collaborators Jun 25, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@davecheney @rsc @gopherbot