cmd/link: malformed mach-o image: segment __DWARF has vmsize < filesize #34935

bolenzhang · 2019-10-16T13:18:25Z

What version of Go are you using (`go version`)?

why not fix this issue #32673 in the version of go1.13?

$ go version
go version go1.13.1 darwin/amd64

Does this issue reproduce with the latest release?

no

What operating system and processor architecture are you using (`go env`)?

go env Output

$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/zhangliyong/Library/Caches/go-build"
GOENV="/Users/zhangliyong/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/zhangliyong/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/zhangliyong/chain/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/rz/4wlrcszd55gf6s2j571bhlzr0000gn/T/go-build990418285=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

Ran a shell script about golang testing.

What did you expect to see?

it works without errors

What did you see instead?

dyld: malformed mach-o image: segment __DWARF has vmsize < filesize

The text was updated successfully, but these errors were encountered:

agnivade · 2019-10-17T04:08:03Z

I don't understand. The fix for #32673 was backported to 1.11 and 1.12. That means it is already there in 1.13. Your issue must be something else. Could you provide more details of how to reproduce this ?

banishee · 2019-10-17T10:53:36Z

Its not work on the MacOS Catalina.
Try to rollback

FUTC-Coding · 2019-10-21T23:42:51Z

I had the same problem, updated go with the newest version from the website and it worked again. Also on MacOS Catalina.

adibrastegarnia · 2019-10-28T15:14:32Z

@agnivade
I have the same problem. My go version is 1.12.5 and yesterday, I upgraded my mac os to 10.15. I cannot upgrade to 1.13 at this moment because we are still using 1.12.X for a project.

To give you an idea, when I source .bashrc or try to run a go program, I am getting that error.

adibrastegarnia · 2019-10-28T16:20:01Z

@agnivade
I don't think it is related to go version. The same error when I upgraded to go 1.13.3 as well on Mac os 10.15.

ianlancetaylor · 2019-10-28T16:48:57Z

Somebody please tell us how to reproduce this. Tell us precisely what you did. Tell us precisely what happened. Thanks.

adibrastegarnia · 2019-10-28T18:02:39Z

Somebody please tell us how to reproduce this. Tell us precisely what you did. Tell us precisely what happened. Thanks.

I will do my best to explain but I did lots of things to make it work.

1- I removed my previous go version by deleting /usr/local/go and /etc/paths.d/go.
2- I installed the golang version 1.13.3 by copying it to /usr/local:
tar -C /usr/local -xzf go1.13.3.darwin-amd64.tar.gz

3- I have these lines in my .bashrc

export GOPATH=/Users/adibrastegarnia/go
export PATH=$PATH:/usr/local/go/bin
export GOROOT=/usr/local/go/
export PATH=$PATH:$GOPATH/bin
export PATH=$PATH:$GOROOT/bin
export GO111MODULE=on

When I tried to run source .bashrc that error happened.

I ended up installing the golang using the pkg installer and it looks normal now. To be honest, I don't know exactly at what conditions that error occurs but I know that is happened when I tried to install it using archive package.

Thanks,
Adib

ianlancetaylor · 2019-10-28T21:56:04Z

If .bashrc contains only the export statements that you listed, I don't see any possible way that sourcing .bashrc could produce the error

dyld: malformed mach-o image: segment __DWARF has vmsize < filesize

We can only fix this problem if we have a way to reproduce this ourselves. Thanks.

(Separately, I recommend very strongly that you not set GOROOT in your .bashrc file. It is only necessary to set GOROOT under special and unusual circumstances. If some of our documentation recommended that you set GOROOT, please let us know, so that we can fix it. Thanks.)

adibrastegarnia · 2019-10-28T22:32:38Z

If .bashrc contains only the export statements that you listed, I don't see any possible way that sourcing .bashrc could produce the error
dyld: malformed mach-o image: segment __DWARF has vmsize < filesize
We can only fix this problem if we have a way to reproduce this ourselves. Thanks.

(Separately, I recommend very strongly that you not set GOROOT in your .bashrc file. It is only necessary to set GOROOT under special and unusual circumstances. If some of our documentation recommended that you set GOROOT, please let us know, so that we can fix it. Thanks.)

I also have a auto-completion call for a go program in .bashrc. Thanks for your recommendation, I will consider it. If I encountered again, I will let you know.

ianlancetaylor · 2019-10-28T23:21:50Z

What program does the auto-completion call try to run? Exactly how was that program built? Thanks.

adibrastegarnia · 2019-10-28T23:26:06Z

What program does the auto-completion call try to run? Exactly how was that program built? Thanks.

It just a go program which has a cli using cobra framework.

ianlancetaylor · 2019-10-29T00:04:29Z

Thanks, but that doesn't help tell us what we need to know.

We can only fix this problem if we have a way to reproduce this ourselves. Thanks.

chaseWillden · 2019-11-01T19:02:59Z

Man I'm getting it too

edjroz · 2019-11-02T04:01:44Z

I’m also receiving this error

loodvn · 2019-11-04T10:38:30Z

Seems to have been fixed in 1.13.4: 26954bd (sorry, didn't know how to link this properly).

Discussion and closed issue: #32673

networkimprov · 2019-11-04T11:48:55Z

That commit actually landed before 1.13 debuted.

thanm · 2019-11-13T19:47:43Z

@bolenzhang It would be nice if we could close this bug out -- any more to do / say here?

gopherbot · 2019-11-17T04:13:52Z

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

xt0fer · 2019-12-18T14:32:14Z

I hit this trying to use a executable from this repo: https://github.com/kyleconroy/sqlc.git
Inside of the project, cd cmd/sqlc; go build; ./sqlc

dyld: malformed mach-o image: segment __DWARF has vmsize < filesize
Abort trap: 6

thanm · 2019-12-18T14:46:22Z

Hi @xt0fer , this issue is closed -- if you are still seeing problems, please open a new issue, including details on how to reproduce (go version, etc). As mentioned previously this should have been fixed in Go 1.13.

xt0fer · 2019-12-18T16:33:51Z

yeah, I should have mentioned this result was using... 1.13.5

networkimprov · 2019-12-18T16:49:14Z

Erm, @thanm the issue closed due to "waiting for info" and @xt0fer just posted a possible reproducer; I think it could be reopened.

thanm · 2019-12-18T18:49:37Z

Erm, @thanm the issue closed due to "waiting for info" and @xt0fer just posted a possible reproducer; I think it could be reopened.

OK, I built a fresh copy of Go from the go1.13 release branch on my macbook, downloaded github.com/kyleconroy/sqlc, did "cd cmd/sqlc; go build; ./sqlc", and I don't see this issue (I just get a usage message). Anything else that I am missing? My machine is running 10.14.6.

xt0fer · 2019-12-18T20:31:20Z

Negative; I was (damn brew) still managing to compile with 1.12.1 here, when I thought I was using 1.13.5 over there. I was able to compile and run fine via 1.13.5. I believe the issue closed and fixed.

thanm · 2019-12-18T20:53:08Z

OK, thanks for confirming that.

itsmontoya · 2020-02-14T17:19:11Z

One of my F/E Engineers are receiving this issue on both 1.12.5 and 1.13.8. Should I have him roll back to 1.13.5?

thanm · 2020-02-14T17:27:24Z

@itsmontoya the fix for this problem has been in Go1.13 since 1.13.1 -- can you please verify that you are indeed using the correct version? Several other folks have posted similarly and in each case the problem was a stale Go version. Thanks.

thanm · 2020-02-14T17:31:14Z

I should add that Go 1.12.5 does not contain the release for this bug, you will need Go 1.12.7 or later.

buihdk · 2020-04-30T13:42:51Z

I still encountered this issue in the Go newest version v1.14.2. I posted an issue here, could someone please check? #38765

agnivade added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Oct 17, 2019

This comment has been minimized.

Sign in to view

ianlancetaylor changed the title ~~dyld: malformed mach-o image: segment __DWARF has vmsize < filesize~~ cmd/linik: malformed mach-o image: segment __DWARF has vmsize < filesize Oct 28, 2019

ianlancetaylor changed the title ~~cmd/linik: malformed mach-o image: segment __DWARF has vmsize < filesize~~ cmd/link: malformed mach-o image: segment __DWARF has vmsize < filesize Oct 28, 2019

ianlancetaylor added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Darwin labels Oct 28, 2019

ianlancetaylor added this to the Go1.14 milestone Oct 28, 2019

ianlancetaylor mentioned this issue Nov 1, 2019

build: dyld: Symbol not found: _fdopendir$INODE64 on OS X 10.9 Mavericks #35269

Closed

miaowing mentioned this issue Nov 9, 2019

mac10.15执行bee 报错 beego/bee#620

Closed

gopherbot closed this as completed Nov 17, 2019

andydotxyz mentioned this issue Jun 4, 2020

dyld: malformed mach-o image: segment __DWARF has vmsize < filesize fyne-io/fyne#1077

Closed

golang locked and limited conversation to collaborators May 18, 2021

gopherbot added the FrozenDueToAge label May 18, 2021

cmd/link: malformed mach-o image: segment __DWARF has vmsize < filesize #34935

cmd/link: malformed mach-o image: segment __DWARF has vmsize < filesize #34935

Comments

bolenzhang commented Oct 16, 2019

What version of Go are you using (go version)?

Does this issue reproduce with the latest release?

What operating system and processor architecture are you using (go env)?

What did you do?

What did you expect to see?

What did you see instead?

agnivade commented Oct 17, 2019

Uh oh!

banishee commented Oct 17, 2019

Uh oh!

FUTC-Coding commented Oct 21, 2019

Uh oh!

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

adibrastegarnia commented Oct 28, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

adibrastegarnia commented Oct 28, 2019

Uh oh!

ianlancetaylor commented Oct 28, 2019

Uh oh!

adibrastegarnia commented Oct 28, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ianlancetaylor commented Oct 28, 2019

Uh oh!

adibrastegarnia commented Oct 28, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ianlancetaylor commented Oct 28, 2019

Uh oh!

adibrastegarnia commented Oct 28, 2019

Uh oh!

ianlancetaylor commented Oct 29, 2019

Uh oh!

chaseWillden commented Nov 1, 2019

Uh oh!

edjroz commented Nov 2, 2019

Uh oh!

loodvn commented Nov 4, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

networkimprov commented Nov 4, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

thanm commented Nov 13, 2019

Uh oh!

gopherbot commented Nov 17, 2019

Uh oh!

xt0fer commented Dec 18, 2019

Uh oh!

thanm commented Dec 18, 2019

Uh oh!

xt0fer commented Dec 18, 2019

Uh oh!

networkimprov commented Dec 18, 2019

Uh oh!

thanm commented Dec 18, 2019

Uh oh!

xt0fer commented Dec 18, 2019

Uh oh!

thanm commented Dec 18, 2019

Uh oh!

itsmontoya commented Feb 14, 2020

Uh oh!

thanm commented Feb 14, 2020

Uh oh!

thanm commented Feb 14, 2020

Uh oh!

buihdk commented Apr 30, 2020

Uh oh!

What version of Go are you using (`go version`)?

What operating system and processor architecture are you using (`go env`)?

adibrastegarnia commented Oct 28, 2019 •

edited

Loading

adibrastegarnia commented Oct 28, 2019 •

edited

Loading

adibrastegarnia commented Oct 28, 2019 •

edited

Loading

loodvn commented Nov 4, 2019 •

edited

Loading

networkimprov commented Nov 4, 2019 •

edited

Loading