delve: could not launch process: EOF

I rollback my CommandLineTools, Temporarily solved the problem by removing new Command Line Tools $ sudo rm -rf /Library/Developer/CommandLineTools

then go to page https://developer.apple.com/download/more/ download and install previous version

Command Line Tools (macOS 10.13) for Xcode 9.2 - Dec 4, 2017

go get -u github.com/derekparker/delve/cmd/dlv will solve this issue.

For those using Homebrew like me, upgrade to the HEAD version:

brew upgrade delve --HEAD

Works on 10.13.4 with latest Command Line Tools 9.3.

Same issue and same MAC OS version, just updated today.

I have a workaround.

sudo rm -rf /Library/Developer/CommandLineTools.

Go to https://developer.apple.com/download/more/ and download Command Line Tools (macos 10.13) for XCode 9.2.

This will restore debugging until the issue gets resolved upstream.

Also had this issue when upgrading to Sierra. What worked for me (assuming you use GoLand IDE).

1. Going to Delve settings in GoLand. Press cmd+shift+a, type “delve”, hit enter.
2. Select box “Use native backend”, hit Apply.
3. After that, debug in GoLand worked for me.

@Khamliuk https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_macOS_10.13_for_Xcode_9.2/Command_Line_Tools_macOS_10.13_for_Xcode_9.2.dmg

and It worked!

For anyone waiting for this patch, you can patch manually like this. Run these instructions inside of the delve package in your $GOPATH/src/github.com/derekparker/delve

git remote add aarzilli git@github.com:aarzilli/delve.git
git pull aarzilli debugserverfix
GO15VENDOREXPERIMENT=1 CERT=dlv-cert make install

If you need to reload your shell exec $SHELL

As I know many of the GoLand users are watching this issue, GoLand 2018.1.1 / 2017.3.4 were rolled-out with the patch from #1169. Thank you to the Delve team for the fix on this.

@姚俊兆 我没有苹果的开发者账号没办法下载那个工具… 能否给我邮箱发一份谢谢120549547@qq.com

@aarzilli I couldn’t follow those instructions for patching gdbserver.go but this seems to work:

diff --git a/pkg/proc/gdbserial/gdbserver.go b/pkg/proc/gdbserial/gdbserver.go
index a201e57..4791f98 100644
--- a/pkg/proc/gdbserial/gdbserver.go
+++ b/pkg/proc/gdbserial/gdbserver.go
@@ -418,6 +418,9 @@ func LLDBLaunch(cmd []string, wd string) (*Process, error) {
 
        p := New(proc.Process)
        p.conn.isDebugserver = isDebugserver
+       if isDebugserver {
+               p.gcmdok = false
+       }
 
        if listener != nil {
                err = p.Listen(listener, cmd[0], 0)

Im on macOS High Sierra 10.13.3 and have same problem!

Here is how I fixed it for GoLang:

1. Build the latest version of dlv: go get -u github.com/derekparker/delve/cmd/dlv
2. Now find your “go/bin” directory, you should see the newly built dlv located in the directory
3. Rename GoLang’s old dlv to dlv.old, my GoLang’s dlv was located in: /Applications/GoLand.app/Contents/plugins/go/lib/dlv/mac/dlv
4. Copy “go/bin/dlv” to /Applications/GoLand.app/Contents/plugins/go/lib/dlv/mac/dlv

For me the problem started from Command Line Tools update, didn’t make update to 10.13.4 yet. So the problem is somewhere in command line tools 😕

IDEA version is 2018.1

As @levrik suggests, for VS Code you can update all of your tools via the Command Pallette. This is accessed via CMD+Shift+P on MacOS, search for Go: Install/Update Tools and tick at least dlv (Debugging) to update delve.

I’m getting this with VS Code. I tried the tip to remove latest XCode - no joy 😦

EDIT: go get -u github.com/derekparker/delve/cmd/dlv worked for me. It would appear VS Code doesn’t use the version brew installs

@henryse, I’d appreciate if you remove the instruction.

1. 2018.1.1 and 2017.3.5 with the fix were released more than a week ago
2. The instruction is harmful since it breaks signature of Goland application and breaks future patch update

Somebody having this problem should try adding conn.gcmdok = false after $GOPATH/src/github.com/derekparker/delve/pkg/proc/gdbserial/gdbserver.go:238. If it doesn’t work, don’t post “it doesn’t work”, turn on logGdbWire and post the output.

@WangChangQin Please move this thread to our tracker at https://youtrack.jetbrains.com/issues/Go but this problem should have been solved in 2018.1.1, a long time ago.

This is my step

1. https://github.com/derekparker/delve
2. cd /Applications/GoLand.app/Contents/plugins/go/lib/dlv/mac
3. mv dlv dlv_back
4. ln -s $GOPATH/bin/dlv dlv

@radugh 's suggestion looked by far the easiest to give a shot and it worked.

I didn’t touch XCode or any OS tools just ran: go get -u github.com/derekparker/delve/cmd/dlv

OS: 10.13.4

$ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables package-id: com.apple.pkg.CLTools_Executables version: 9.3.0.0.1.1521514116 volume: / location: / install-time: 1525178199 groups: com.apple.FindSystemFiles.pkg-group

$ gcc --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 9.1.0 (clang-902.0.39.2) Target: x86_64-apple-darwin17.5.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

@charnlsxy the bug was fixed in 2018.1.1, not in 2018.1. Let’s continue the discussion at https://youtrack.jetbrains.com to avoid spamming other Delve’s users, please.

@RoarkeRandall could be. My app store wants to upgrade it again but I just declined the terms and conditions when they showed up. Now it waits for manual approve.

Weird, I down graded the CLI tools like @YaoJunZhao suggested and it worked, but this morning its no longer working. I wonder if macOS automatically upgraded the cli tools again?

So I downloaded the latest master and ran a debug session and it worked fine. But the version from brew does not work.

EDIT: Ok, turns out the latest does not work either. Changing p.gcmdok = true fixes the issue for me. But I have no idea what this does.

Posting logs with just logGdbWire = true

Current Version Delve Debugger Version: 1.0.0 Build: db435c184eb79976087fc0cb36c2867c737a9066

This one with p.gcmdok unmodified log_broken.txt

This one with p.gcmdok = false log_working.txt