Command failed: protocol error E09 during set breakpoint for packet #1116

alphaaleph · 2018-02-05T21:28:52Z

Please answer the following before submitting your issue:

Note: Please include any substantial examples (debug session output,
stacktraces, etc) as linked gists.

What version of Delve are you using (dlv version)?
What version of Go are you using? (go version)?
What operating system and processor architecture are you using?
What did you do?
What did you expect to see?
What did you see instead?

ANSWERS:

dlv Version: 1.0.0-rc.2
go version go1.9.3 darwin/amd64
Mac OSX Sierra 10.12.6
Run debugger against go project, and enter:
b main.go:8 (line 8 exists)
Not an error when I hit enter. :-)
An error: protocol error E09

Other info: This happens in the work Mac. I have my home Mac running the same setup as above, and it works in that machine. So I was thinking, permission problem with the work Mac? But I also have a setup running in Archlinux in my Parallels Desktop, inside my work Mac; and that version runs!!??

The Parallels VM info is:

dlv Version: 1.0.0-rc.1
go version go1.8.5 linux/amd64
4.7.4.1-ARCH

So it works in home Mac, and it works in work Mac running Linux VM; but it doesn't work in work Mac..!!?? Any ideas? I'll try to trace the delve code when I have a chance.

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

aarzilli · 2018-02-06T12:02:48Z

So I was thinking, permission problem with the work Mac?

That's likely, debugservice can not set software breakpoints.

hankjacobs · 2018-03-06T23:02:35Z

For what its worth, I had the same issue and determined it was due to Cylance (an antivirus / malware / security app). Whitelisting /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/debugserver did the trick.

aarzilli · 2018-05-23T11:22:41Z

Closing, likely not (our) bug.

jessesuen · 2018-07-31T20:23:00Z

Thank you @hankjacobs! This was infuriating.

shlomi-dr · 2021-07-03T00:20:35Z

For what its worth, I had the same issue and determined it was due to Cylance (an antivirus / malware / security app). Whitelisting /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/debugserver did the trick.

I am experiencing the same problem, but I can't find anything to whitelist this in (no Cylance or other things that I know of, and the laptop is fresh out of the store, so no corporate stuff). Googling this problem returns literally only this page, so I thought I might as well ask for help here.

Here are the versions I have installed, and the error I am seeing:

> go version
go version go1.16.5 darwin/amd64
> dlv version
Delve Debugger
Version: 1.6.1
Build: $Id: 114218c22f3791287c4bc2f4ff35a846a1416ee9 $
> sw_vers
ProductName:    macOS
ProductVersion: 11.4
BuildVersion:   20F71
> dlv debug cmd/main.go
Type 'help' for list of commands.
(dlv) b main.main
Command failed: protocol error E09 during set breakpoint for packet $Z0,7ffd012df4fb,4

Perhaps you could help me root cause this? Or maybe point me someplace I can get help?

Thanks!

Found solution

It seems that on M1 mac laptops, we need to install the ARM version of go and not the AMD version:

Go to https://golang.org/dl/
Look for the installer for MacOS that is on ARMv8 architecture, eg. go1.16.6.darwin-arm64.pkg
Download and install
Make sure the rest of the go-tools are setup (vscode does this automatically)

Now, lets try again:

> go version
go version go1.16.6 darwin/arm64
> dlv version
Delve Debugger
Version: 1.6.1
Build: $Id: 114218c22f3791287c4bc2f4ff35a846a1416ee9 $
> sw_vers
ProductName:	macOS
ProductVersion:	11.4
BuildVersion:	20F71
> dlv debug cmd/main.go
Type 'help' for list of commands.
(dlv) b main.main
Breakpoint 1 (enabled) set at 0x102cf67e0 for main.main() ./cmd/main.go:23
(dlv) c
> main.main() ./cmd/main.go:23 (hits goroutine(1):1 total:1) (PC: 0x102cf67e0)
    18:			fmt.Printf("Usage: %s %s\n", os.Args[0], strings.Join(arg, " "))
    19:			os.Exit(1)
    20:		}
    21:	}
    22:
=>  23:	func main() {
    24:		println("Test module")
    25:		checkArgs("<arg1>", "<arg2>")
    26:
    27:		logger := logger.NewLogger()
    28:		config, err := config.ReadConfig(logger)
(dlv)

Success! 🥳

steve7688 · 2022-03-18T06:04:28Z

Hey guys I am using go version go1.18 darwin/arm64 but still get an error

protocol error E09 during set breakpoint for packet $Z0,7ff701704851,4

when I set a breakpoint

I just use goland

muzig · 2022-04-06T07:47:02Z

export GOOS=darwin
export GOARCH=arm64

then restart goland，maybe useful

yongliu1992 · 2022-05-10T08:40:03Z

export GOOS=darwin export GOARCH=arm64

thanks,useful

josiahcoad · 2022-10-27T18:52:24Z

Hey still not working for me on M1 Mac with Vscode. Spent hours on this already.

I am able to get dlv working from command line. ie, if i type dlv debug main.go, a dlv interpreter appears that I can successfully set breakpoints and step through code. The problem comes when I try to set breakpoint in VSCode, the breakpoint goes gray with error message protocol error E09 during set breakpoint for packet $Z0,7ff800d20a09,4. The program runs normally.

>>> which dlv
dlv: aliased to /Users/jcoad/go/bin/dlv
>>> dlv version
Delve Debugger
Version: 1.9.1
Build: $Id: d81b9fd12bfa603f3cf7a4bc842398bd61c42940
>>> echo $GOOS $GOARCH
darwin arm64
>>> go version
go version go1.19.2 darwin/arm64

derekparker · 2022-10-27T19:32:27Z

@hyangah @suzmue @polinasok

thanhdatvo · 2022-11-07T19:16:15Z

I had same problem.
The problem may be because I installed go using both brew and .pkg file
I fixed it by removing usr/local/go then I restarted the vscode
The go debugger's breakpoints work again

groggy7 · 2024-01-11T12:58:20Z

I had same problem and i figured out it was because i mistakenly installed x86 version of Go while updating.

danielshmbg · 2024-03-05T05:17:53Z

Try adding additional config in launch.json, somehow it’s working just fine on my laptop.

 "configurations": [
  {
    ...
    "logOutput": "dap",
    "showLog": false
  }
 ]

raz-cohen · 2024-09-22T21:41:11Z

For what its worth, I had the same issue and determined it was due to Cylance (an antivirus / malware / security app). Whitelisting /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/debugserver did the trick.

I am experiencing the same problem, but I can't find anything to whitelist this in (no Cylance or other things that I know of, and the laptop is fresh out of the store, so no corporate stuff). Googling this problem returns literally only this page, so I thought I might as well ask for help here.

Here are the versions I have installed, and the error I am seeing:
> go version
go version go1.16.5 darwin/amd64
> dlv version
Delve Debugger
Version: 1.6.1
Build: $Id: 114218c22f3791287c4bc2f4ff35a846a1416ee9 $
> sw_vers
ProductName:    macOS
ProductVersion: 11.4
BuildVersion:   20F71
> dlv debug cmd/main.go
Type 'help' for list of commands.
(dlv) b main.main
Command failed: protocol error E09 during set breakpoint for packet $Z0,7ffd012df4fb,4
Perhaps you could help me root cause this? Or maybe point me someplace I can get help?

Thanks!

Found solution

It seems that on M1 mac laptops, we need to install the ARM version of go and not the AMD version:

Go to https://golang.org/dl/

Look for the installer for MacOS that is on ARMv8 architecture, eg. go1.16.6.darwin-arm64.pkg

Download and install

Make sure the rest of the go-tools are setup (vscode does this automatically)

Now, lets try again:
> go version
go version go1.16.6 darwin/arm64
> dlv version
Delve Debugger
Version: 1.6.1
Build: $Id: 114218c22f3791287c4bc2f4ff35a846a1416ee9 $
> sw_vers
ProductName:	macOS
ProductVersion:	11.4
BuildVersion:	20F71
> dlv debug cmd/main.go
Type 'help' for list of commands.
(dlv) b main.main
Breakpoint 1 (enabled) set at 0x102cf67e0 for main.main() ./cmd/main.go:23
(dlv) c
> main.main() ./cmd/main.go:23 (hits goroutine(1):1 total:1) (PC: 0x102cf67e0)
    18:			fmt.Printf("Usage: %s %s\n", os.Args[0], strings.Join(arg, " "))
    19:			os.Exit(1)
    20:		}
    21:	}
    22:
=>  23:	func main() {
    24:		println("Test module")
    25:		checkArgs("<arg1>", "<arg2>")
    26:
    27:		logger := logger.NewLogger()
    28:		config, err := config.ReadConfig(logger)
(dlv)
Success! 🥳

Goshhh, you just helped me.
Tnx!
For anyone who's encountering this issue, I highly suggest to first try and match the correct Go 'version' (arm\amd etc...)

aarzilli added area/proc/gdbserial os/macOS kind/needs more info labels Feb 6, 2018

aarzilli closed this as completed May 23, 2018

kkrime mentioned this issue Mar 19, 2022

Hey guys I am using go version go1.18 darwin/arm64 but still get an error #2935

Closed

aarzilli mentioned this issue Mar 19, 2022

Getting: Command failed: protocol error E09 during set breakpoint for packet when trying to set break point #2936

Closed

aarzilli mentioned this issue Apr 11, 2022

Command failed: protocol error E09 during set breakpoint for packet (M1 Mac) #2967

Closed

junhee071 mentioned this issue Aug 30, 2022

Delve debugger not working on VS Code - panic: assignment to entry in nil map #3120

Closed

aarzilli mentioned this issue Oct 24, 2023

Goland Debug Problem: protocol error E09 during set breakpoint for packet #3537

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Command failed: protocol error E09 during set breakpoint for packet #1116

Command failed: protocol error E09 during set breakpoint for packet #1116

alphaaleph commented Feb 5, 2018

aarzilli commented Feb 6, 2018

hankjacobs commented Mar 6, 2018

aarzilli commented May 23, 2018

jessesuen commented Jul 31, 2018

shlomi-dr commented Jul 3, 2021 •

edited

Loading

steve7688 commented Mar 18, 2022 •

edited

Loading

muzig commented Apr 6, 2022

yongliu1992 commented May 10, 2022

josiahcoad commented Oct 27, 2022 •

edited

Loading

derekparker commented Oct 27, 2022

thanhdatvo commented Nov 7, 2022 •

edited

Loading

groggy7 commented Jan 11, 2024

danielshmbg commented Mar 5, 2024

raz-cohen commented Sep 22, 2024

Found solution

Command failed: protocol error E09 during set breakpoint for packet #1116

Command failed: protocol error E09 during set breakpoint for packet #1116

Comments

alphaaleph commented Feb 5, 2018

aarzilli commented Feb 6, 2018

hankjacobs commented Mar 6, 2018

aarzilli commented May 23, 2018

jessesuen commented Jul 31, 2018

shlomi-dr commented Jul 3, 2021 • edited Loading

Found solution

steve7688 commented Mar 18, 2022 • edited Loading

muzig commented Apr 6, 2022

yongliu1992 commented May 10, 2022

josiahcoad commented Oct 27, 2022 • edited Loading

derekparker commented Oct 27, 2022

thanhdatvo commented Nov 7, 2022 • edited Loading

groggy7 commented Jan 11, 2024

danielshmbg commented Mar 5, 2024

raz-cohen commented Sep 22, 2024

Found solution

shlomi-dr commented Jul 3, 2021 •

edited

Loading

steve7688 commented Mar 18, 2022 •

edited

Loading

josiahcoad commented Oct 27, 2022 •

edited

Loading

thanhdatvo commented Nov 7, 2022 •

edited

Loading