cmd/link: missing debug_frame section if package plugin is imported #23733

aarzilli · 2018-02-07T19:17:41Z

Please answer these questions before submitting your issue. Thanks!

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

go version devel +00587e8 Fri Jan 26 23:55:04 2018 +0000 linux/amd64

but this also happens with the latest release candidate for 1.10.

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

GOARCH="amd64"
GOBIN=""
GOCACHE="/home/a/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/a/n/go/"
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build091711191=/tmp/go-build -gno-record-gcc-switches"

What did you do?

Compile anything that imports plugin:

package main

import (
	"plugin"
	"fmt"
)

func main() {
	test := plugin.Plugin{}
	fmt.Println(test)
}

The executable used to have .debug_frame in 1.9 but has eh_frame now.

Was this done intentionally?

(originally reported as https://github.com/derekparker/delve/issues/1118)

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

heschi · 2018-02-07T21:32:19Z

.eh_frame is a red herring; I'm fairly certain that the external linker is adding that because .debug_frame is missing and it doesn't know where to put its own stuff. The real issue is that .debug_frame is missing entirely in 1.10.

Bisects to 24e4a12, which I think may have been a little overzealous; we could have kept some of the DWARF. But it's not going to be a good debugging experience regardless.

cc @crawshaw

aarzilli · 2018-02-07T21:40:02Z

Got it, thanks for looking into it. I see now that it doesn't really have a debug_info section either.

gopherbot · 2018-05-03T12:18:42Z

Change https://golang.org/cl/111237 mentions this issue: cmd/link: move dwarf part of DWARF generation before type name mangling

gopherbot · 2018-05-03T12:20:24Z

Change https://golang.org/cl/111236 mentions this issue: cmd/link: move type name mangling after deadcode elimination

chaplin89 · 2018-05-05T13:46:34Z

Is there any workaround for this?

OliviaSong · 2018-05-06T08:45:44Z

I encountered this problem . project really have a plugin package. Which version is good?

heschi · 2018-05-07T19:16:10Z

There is no workaround other than to remove the plugin dependency, sorry. The Go 1.11 freeze was a week ago, so the CLs above will have to wait for 1.12.

chaplin89 · 2018-05-08T06:50:07Z

Thanks

VmFree · 2018-05-24T13:10:12Z

no fix for this problem? I also encountered such problem under ubuntu 16.4

tty5 · 2018-06-19T02:17:51Z

any update for thsi bug?

heschi · 2018-06-19T20:22:58Z

As I said above, there will be no updates until the 1.12 development cycle opens. That will be in August; see https://github.com/golang/go/wiki/Go-Release-Cycle.

vladbarosan · 2018-06-22T20:51:31Z

Please prioritize this as it blocks debugging applications with plugins.

ianlancetaylor · 2018-06-23T00:04:47Z

@vladbarosan We'll do our best but to be honest we have few resources to improve the plugin development experience. Go is an open source project, and this is an area where external contributions would be very valuable.

…port. (NB: Should be compatible with dlv when run under go 1.9, however due to golang/go#23733 go 1.10 and 1.11 will cause dlv to produce an error)

Debugging Hydra in Go 1.10 and 1.11 (confirmed by one of its members), is not possible due to [this unresolved bug](golang/go#23733) which is related to the use of the plugin functionality. This change allows passing a build tag which will disable plugin implementation and therefore allow to debug in all the use-cases where plugin backend is not needed. Signed-of-by: Gorka Lerchundi Osa <glertxundi@gmail.com>

Debugging Hydra in Go 1.10 and 1.11 (confirmed by one of its members), is not possible due to [this unresolved bug](golang/go#23733) which is related to the use of the plugin functionality. This change allows passing a build tag which will disable plugin implementation and therefore allow to debug in all the use-cases where plugin backend is not needed. Signed-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com>

Moves type name mangling after deadcode elimination. The motivation for doing this is to create a space between deadcode elimination and type name mangling where DWARF generation for types and variables can exist, to fix issue #23733. Change-Id: I9db8ecc0f4efe3df6c1e4025f02642fd452f9a39 Reviewed-on: https://go-review.googlesource.com/111236 Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Cherry Zhang <cherryyz@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>

juhwany · 2018-09-06T07:08:48Z

@ianlancetaylor
I've encountered same problem. Is this issue solved? then which go version should I use for debugging plugin?

ianlancetaylor · 2018-09-06T14:27:37Z

@juhwany This issue is reportedly closed on tip. Would you be able to try that out and see?

juhwany · 2018-09-06T14:39:44Z

@ianlancetaylor

OK let me try. But which Go version should I use for testing?

sh0umik · 2018-09-10T18:55:00Z

Having the same problem after upgrading from golang10.0 to golang11.1

hongliang5316 · 2018-09-21T16:08:41Z

How about to solve this problem?

JVerwolf · 2018-09-27T17:45:46Z

I solved this problem by downgrading my GO version from 1.11 to 1.10.4. I'm on Ubuntu 16.4, and I fixed this problem by I deleting my /usr/local/go directory, downloading 1.10.4, then extracting with tar -C /usr/local -xzf go1.10.4.linux-amd64.tar.gz. IntelliJ debugger worked fine afterwards. Hope this helps.

heschi · 2018-09-27T17:51:50Z

Nothing about this bug was supposed to change, certainly not get worse, with the upgrade to 1.11. Importing the plugin package should have disabled debugging in both. If you have a program that uses plugins that is debuggable in 1.10 but not in 1.11, please give precise instructions to reproduce the problem here. If the program doesn't use plugin, it's not this issue, and it would help to file a new one, again with a reproducer. Thanks.

GodloveD · 2018-09-29T19:53:36Z

Why is this issue closed? Seems like it is still a problem no?

aarzilli · 2018-09-29T20:24:51Z

@GodloveD it should be fixed in 1.12

wenjun001 · 2018-10-14T17:07:38Z

I just try 1.9 works fine 1.10 and 1.11 has this kind of problem

heschi · 2018-10-15T17:09:19Z

@wenjun001 Please see my comments in #23733 (comment). Nobody can do anything to help without more detail.

heschi added the Debugging label Feb 7, 2018

aarzilli mentioned this issue Feb 8, 2018

support eh_frame if debug_frame is not present go-delve/delve#1118

Closed

aarzilli mentioned this issue Feb 23, 2018

dlv does not work when app uses plugin go-delve/delve#1133

Closed

aarzilli mentioned this issue Mar 6, 2018

could not launch process: decoding dwarf section info at offset 0x0: too short go-delve/delve#1138

Closed

ianlancetaylor added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Mar 28, 2018

ianlancetaylor added this to the Unplanned milestone Mar 28, 2018

ianlancetaylor added the help wanted label Jun 23, 2018

aarzilli mentioned this issue Jul 18, 2018

could not launch process: could not get .debug_frame section: could not find .debug_frame section go-delve/delve#1269

Closed

magik6k mentioned this issue Jul 22, 2018

build tag to disable dynamic plugins ipfs/kubo#5274

Merged

glerchundi mentioned this issue Aug 13, 2018

config: disable plugin backend through 'noplugin' tag ory/hydra#986

Merged

gopherbot closed this as completed in 9c83383 Sep 4, 2018

complyue mentioned this issue Sep 5, 2018

Stop shipping imports/plugin.go for debuggability by default cosmos72/gomacro#37

Closed

electricmonk mentioned this issue Sep 22, 2018

Debugger doesn't start in GoLand orbs-network/orbs-network-go#245

Closed

gitlw mentioned this issue Oct 30, 2018

Tutorial to explain how to launch the project in debug mode dgraph-io/dgraph#2704

Closed

aarzilli mentioned this issue Dec 7, 2018

Delve fails when "plugin" package is included go-delve/delve#1439

Closed

jmigpin mentioned this issue Jan 25, 2019

debugging editor using dlv debugger jmigpin/editor#15

Closed

kkasravi mentioned this issue Feb 12, 2019

Upgrade to go 1.12, remove 'static', 'plugins' macros in kfctl (golang) kubeflow/kubeflow#2460

Closed

sbueringer mentioned this issue Feb 14, 2019

Problems with Go 1.10/1.11 debugging OPA with delve open-policy-agent/opa#1210

Closed

tswift242 mentioned this issue Mar 5, 2019

Restoring containers from a custom checkpoint-dir is broken containerd/containerd#2406

Closed

golang locked and limited conversation to collaborators Oct 15, 2019

gopherbot added the FrozenDueToAge label Oct 15, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

cmd/link: missing debug_frame section if package plugin is imported #23733

cmd/link: missing debug_frame section if package plugin is imported #23733

aarzilli commented Feb 7, 2018

heschi commented Feb 7, 2018

aarzilli commented Feb 7, 2018

gopherbot commented May 3, 2018

gopherbot commented May 3, 2018

chaplin89 commented May 5, 2018

OliviaSong commented May 6, 2018

heschi commented May 7, 2018

chaplin89 commented May 8, 2018

VmFree commented May 24, 2018

tty5 commented Jun 19, 2018

heschi commented Jun 19, 2018

vladbarosan commented Jun 22, 2018

ianlancetaylor commented Jun 23, 2018

juhwany commented Sep 6, 2018

ianlancetaylor commented Sep 6, 2018

juhwany commented Sep 6, 2018 •

edited

sh0umik commented Sep 10, 2018

hongliang5316 commented Sep 21, 2018

JVerwolf commented Sep 27, 2018

heschi commented Sep 27, 2018

GodloveD commented Sep 29, 2018

aarzilli commented Sep 29, 2018

wenjun001 commented Oct 14, 2018

heschi commented Oct 15, 2018

cmd/link: missing debug_frame section if package plugin is imported #23733

cmd/link: missing debug_frame section if package plugin is imported #23733

Comments

aarzilli commented Feb 7, 2018

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

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

What did you do?

heschi commented Feb 7, 2018

aarzilli commented Feb 7, 2018

gopherbot commented May 3, 2018

gopherbot commented May 3, 2018

chaplin89 commented May 5, 2018

OliviaSong commented May 6, 2018

heschi commented May 7, 2018

chaplin89 commented May 8, 2018

VmFree commented May 24, 2018

tty5 commented Jun 19, 2018

heschi commented Jun 19, 2018

vladbarosan commented Jun 22, 2018

ianlancetaylor commented Jun 23, 2018

juhwany commented Sep 6, 2018

ianlancetaylor commented Sep 6, 2018

juhwany commented Sep 6, 2018 • edited

sh0umik commented Sep 10, 2018

hongliang5316 commented Sep 21, 2018

JVerwolf commented Sep 27, 2018

heschi commented Sep 27, 2018

GodloveD commented Sep 29, 2018

aarzilli commented Sep 29, 2018

wenjun001 commented Oct 14, 2018

heschi commented Oct 15, 2018

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

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

juhwany commented Sep 6, 2018 •

edited