cb65877297
* Add --continue to continue process on launch/attach * Add small test of --continue * regenerate usage docs * minor cleanup * Use similar approach to `trace` and connect and detach using a client instance * back out previous attempt * regen usage doc * fix up continue test * fix TestContinue to properly test --continue * back out unnecessary changes * update faq
1.7 KiB
Frequently Asked Questions
I'm getting an error while compiling Delve / unsupported architectures and OSs
The most likely cause of this is that you are running an unsupported Operating System or architecture. Currently Delve supports Linux, Windows and macOS on the amd64 architecture (also known as Intel 86x64).
For example if you are getting the undefined: ArchInst error message while compiling Delve, that means that Delve doesn't currently support your processor architecture.
There is no planned ETA for support of other architectures or operating systems. Bugs tracking requested support are:
How do I use Delve with Docker?
When running the container you should pass the --security-opt=seccomp:unconfined option to Docker. You can start a headless instance of Delve inside the container like this:
dlv exec --headless --listen :4040 /path/to/executable
And then connect to it from outside the container:
dlv connect :4040
The program will not start executing until you connect to Delve and send the continue command. If you want the program to start immediately you can do that by passing the --continue and --accept-multiclient options to Delve:
dlv exec --headless --continue --listen :4040 --accept-multiclient /path/to/executable
Note that the connection to Delve is unauthenticated and will allow arbitrary remote code execution: do not do this in production.