Closed samuelsinayoko closed 4 months ago
After some testing seams to be related to dape switching connection method with debugpy.
Please test how the following works for you:
debugpy-module command-args ("-m" "debugpy.adapter" "--host" "0.0.0.0" "--port" :autoport) port :autoport :cwd "/Users/sinayoks/dev/hello/" :module "example"
This change has been reverted, but the debugging experience for sub processes has been OK for one sub process but when the number grows as in your examples dape is not really that useful, but your issue motivated me to fix that. So I will have something ready in a few days.
Note sub process not threads, thread support should works with dape but sub process are handled by debugpy in an uniq way
Tested your changes using commit 339cdef7d5f76da2cdaa2b679bb07e5ce8830edf and it now works on OSX s! Amazing stuff thanks so much @svaante! Am now able to hit the breakpoints in subprocesses.
Hey, I have pushed some changes that should make the multi process debuggin in debugpy useful
Closing as it seams to be working
Does dape support Python code that uses multiprocessing? See example code below
expected output
I'm able to hit the breakpoint when using a single worker/process (so no multiprocessing), but getting an operation not permitted error with 2 processes/threads when running this with
M-x dape
(`debugpy-module :cwd "/Users/sinayoks/dev/hello/" :module "example")Here's the
*dape-repl*
outputand the
*dape-events