You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Navigate to the built OCaml bytecode executable in VS Code Explorer panel (a .bc file in _build directory), right click on it and select "Start OCaml Debugging (experimental)".
The debugger launches immediately.
On Windows 11, it runs the following command in the powershell terminal:
c:; cd 'c:\Users\[name]\source\repos\shortrounddev\Haruko\_build\default\bin'; ${env:CAML_DEBUG_SOCKET}='127.0.0.1:56183'; & 'c:\Users\[name]\source\repos\shortrounddev\Haruko\_build\default\bin\main.bc'
Which seems to launch a detached debugger client but no debugger (I suspect because trying to run a .bc file directly with no program associated does nothing).
Additionally, the generated launch.json file similarly does nothing:
{
// Use IntelliSense to learn about possible attributes.// Hover to view descriptions of existing attributes.// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387"version": "0.2.0",
"configurations": [
{
"name": "OCaml earlybird (experimental)",
"type": "ocaml.earlybird",
"request": "launch",
"program": "${command:AskProgram}",
"stopOnEntry": true
}
]
}
Pops up an info box in the bottom right which says:
File system provider for c:%5CUsers%5C[name]%5Csource%5Crepos%5Cshortrounddev%5CHaruko is not available.
Are there up to date instructions for how to launch the debugger?
The text was updated successfully, but these errors were encountered:
In the documentation for the VSCode extension, it says:
On Windows 11, it runs the following command in the powershell terminal:
Which seems to launch a detached debugger client but no debugger (I suspect because trying to run a .bc file directly with no program associated does nothing).
Additionally, the generated launch.json file similarly does nothing:
Pops up an info box in the bottom right which says:
Are there up to date instructions for how to launch the debugger?
The text was updated successfully, but these errors were encountered: