Application Logs not visible after 3b796163591a300a433e25384f2574419e51da1a

[sanchay9]

Breakpoints and debugging works, but logs are not visible in dap-repl buffer.

[sanchay9]

upd: I can see the logs divided into stderr and stdout log files in .cache/nvim on :DapShowLog

how can I have all these in dap-repl buffer just like before.

[mfussenegger]

What's the use-case for seeing the stderr/stdout of the debug adapter in the REPL?

Any output from debug adapters that's supposed to be visible to the end-user should go through output events.

[zivkovicn]

@mfussenegger I think that @sanchay9 mean to say, he was expecting to see the logs in the console pane (right of the REPL pane) in dap ui

[mfussenegger]

Showing an empty window isn't telling me much but I think I can put the puzzle pieces together now.

It looks like delve by default doesn't use output events, so you were relying on stdout/stderr being sent to the REPL to see the stdout of your application. nvim-dap so far only did that as a workaround.

But there's a outputMode = "remote" option for delve to get it to use output events.

E.g.:

dap.configurations.go = {
  {
    type = "delve",
    name = "file",
    request = "launch",
    program = "${file}",
    outputMode = "remote",
  }
}

See go-delve/delve#3253

[sanchay9]

yes, that was the case, after adding remote option, I can see the logs again. Appreciate the detailed explanation, thanks!