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

cmd/ld: -s produces broken binary #6371

Closed
josharian opened this issue Sep 12, 2013 · 2 comments
Closed

cmd/ld: -s produces broken binary #6371

josharian opened this issue Sep 12, 2013 · 2 comments

Comments

@josharian
Copy link
Contributor

What steps will reproduce the problem?

1. go get github.com/josharian/gostripbug
2. cd $GOPATH/src/github.com/josharian/gostripbug
3. make

What is the expected output?

Hello

What do you see instead?

runtime: function symbol table header: 0x0x0 0x0x0
fatal error: invalid function symbol table


runtime stack:

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

6g, 6l. Also reproduces with 5g, 5l. Haven't tried others.

Which operating system are you using?

OS X, arm/linux.

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

go version devel +75118231847b Thu Sep 12 00:15:28 2013 +0200 darwin/amd64

Please provide any additional information below.

Does not reproduce with Go 1.1.

I'd love to know for future reference -- if I wanted to write a test case for this in
the Go source tree (so I could reference a CL that others could build on instead of
making a separate GitHub repo), where would it belong?
@minux
Copy link
Member

minux commented Sep 12, 2013

Comment 1:

i think the symbol table is necessary for Go 1.2 program to run, so -s might not
be able to strip the symbol table anymore. in that case, perhaps it's better to remove
the function (-s).

Labels changed: added priority-soon, removed priority-triage.

Status changed to Accepted.

@alexbrainman
Copy link
Member

Comment 2:

Dup. Isn't it?
Alex

Status changed to Duplicate.

Merged into issue #6245.

@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.
Projects
None yet
Development

No branches or pull requests

4 participants