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.

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

cmd/go: occasional stack corruption on arm64 (process related?) #7326

Closed
mwhudson opened this issue Feb 14, 2014 · 4 comments
Closed

cmd/go: occasional stack corruption on arm64 (process related?) #7326

mwhudson opened this issue Feb 14, 2014 · 4 comments
Labels
FrozenDueToAge

Comments

@mwhudson
Copy link
Contributor 

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. go install launchpad.net/juju-core/... on an arm64 system
2. about 1 time in 10 it panics

Which compiler are you using (5g, 6g, 8g, gccgo)?

gccgo.

Which operating system are you using?

Ubuntu Trusty on an arm64 system

Which version are you using?  (run 'go version')

A patched version of the go tool from 1.2

Please provide any additional information below.

I'm posting this here in case anyone (well, OK: Ian) has any crazy ideas as to what
might be causing this.  There is a bit more information at
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1279620.  Basically it seems that
something inside of os/exec.Cmd.Run eats the stack when parallelism is involved.
@mwhudson
Copy link
Contributor Author

Comment 1:

It seems neither parallelism or GC are required to have this happen, but it sure happens
a lot more with both of them.

@mwhudson
Copy link
Contributor Author

Comment 2:

It seems to be to do with signal handling -- if I prevent SIGCHLD from reaching the
process with gdb, it works (also, one of the values that tends to end up on the stack is
0x11, which is SIGCHLD).

@mwhudson
Copy link
Contributor Author

Comment 3:

Turns out this is a glibc bug: https://sourceware.org/bugzilla/show_bug.cgi?id=16629

@minux
Copy link
Member

minux commented Feb 24, 2014

Comment 4:

so this issue could be closed, if you disagree please comment.

Status changed to Retracted.

@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
@minux @mwhudson @gopherbot