debugger fails with could not launch process: stub exited while waiting for connection: exit status 0 on M1 Pro

[thidasapankaja]

Please answer the following before submitting your issue:

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

If this is about source listing not showing up (or breakpoints not being
accepted) while running in a container please read our
FAQ
first.

1. What version of Delve are you using (dlv version)?

Delve Debugger
Version: 1.9.0
Build: $Id: 69310c2f438e492f892d6af22e8e62c8ea1e9d8d $

2. What version of Go are you using? (go version)?
   go version go1.18.3 darwin/arm64
3. What operating system and processor architecture are you using?

MacBook Pro (14-inch, 2021)
Apple M1 Pro

4. What did you do?

package main

import "fmt"

func main() {
	fmt.Println("Hello, World")
}

5. What did you expect to see?

run the dlv without any error

6. What did you see instead?

could not launch process: stub exited while waiting for connection: exit status 0

Already followed the installation guide and already had xcode-select installed, enabled Developer Mode and added the user to the Developer Group

[aarzilli]

This is almost certainly a problem with your computer. You can confirm it by locating the executable of debugserver (it should be /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/debugserver) and running it manually on an executable file: path_to_debugserver 127.0.0.1:31337 path_to_some_executable.
It will fail instead of waiting for a connection.

[thidasapankaja]

@aarzilli It returns this

debugserver-@(#)PROGRAM:LLDB  PROJECT:lldb-1316.0.9.46
 for x86_64 (running under translation).
Usage:
  debugserver host:port [program-name program-arg1 program-arg2 ...]
  debugserver /path/file [program-name program-arg1 program-arg2 ...]
  debugserver host:port --attach=<pid>
  debugserver /path/file --attach=<pid>
  debugserver host:port --attach=<process_name>
  debugserver /path/file --attach=<process_name>

[aarzilli]

You didn't call it correctly, please see my message or the usage message it's printing.

[thidasapankaja]

I ran it from the path of main.go
sudo /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/debugserver 127.0.0.1:31337 .

and getting this error

debugserver-@(#)PROGRAM:LLDB  PROJECT:lldb-1316.0.9.46
 for x86_64 (running under translation).
error: failed to launch process /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/debugserver: Permission denied
Exiting.

I already added user to the Developer group following this command

sudo dscl . append /Groups/_developer GroupMembership $(whoami)

[aarzilli]

The second argument needs to be the path to an executable, even better if it's a go executable you built to rule out the case were the problem is with permissions. Also no sudo.

[thidasapankaja]

Getting the same error running this
/Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/debugserver 127.0.0.1:31337 main.go

[aarzilli]

main.go isn't an executable.

[thidasapankaja]

@aarzilli sorry. I'm a bit confused. Shouldn't this be .go file ?

EDIT : ran it on build go project as /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/debugserver 127.0.0.1:31337 ./hello and it's getting this (os/kern) invalid argument error.

[aarzilli]

No, dmg files aren't executable either. An executable is the output file of go build, for example.

[thidasapankaja]

@aarzilli Yea, I updated the answer, getting this as the error now

debugserver-@(#)PROGRAM:LLDB  PROJECT:lldb-1316.0.9.46
 for x86_64 (running under translation).
error: failed to launch process /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/debugserver: (os/kern) invalid argument
Exiting.

[aarzilli]

Ok, debugserver is failing on its own, without any interaction with delve. This is a problem with your setup. Closing.

[aarzilli]

PS. I noticed this:

debugserver-@(#)PROGRAM:LLDB  PROJECT:lldb-1316.0.9.46
 for x86_64 (running under translation).

[thidasapankaja]

@aarzilli
Ok. I just ran this

arch -arm64 /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/debugserver 127.0.0.1:31337 ./hello

and it is waiting for a connection

debugserver-@(#)PROGRAM:LLDB  PROJECT:lldb-1316.0.9.46
 for arm64.
Listening to port 31337 for a connection from 127.0.0.1...

[exosyphon]

@thidasapankaja did you ever get this working? I am at the same point right now that you left off

[exosyphon]

I figured out my issue. #3804