bjoli/lsp-bjolang
SHA256
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Debugging with dape and netcoredbg, and the compiler's new options

Browse source 
emacs/bjolang-dape.el adds a dape configuration that builds the current
file with -d and runs it under netcoredbg, launching dotnet with the
program, which is a managed assembly rather than a native host. The
README says what a debugger shows today.

The check builds its options from Build.dependencyOptions, now that the
compiler's options have grown the dump flags.

🤖 Generated with [ECA](https://eca.dev)

Co-Authored-By: eca-agent <git@eca.dev>
This commit is contained in:
Linus Björnstam 2026-10-16 09:35:25 +02:00
parent c6f357c6f8
commit 77b8a92e03
3 changed files with 77 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

13
README.md
View file

@ -94,6 +94,19 @@ stdout, and logs to stderr.
(add-hook 'bjo-mode-hook #'lsp)
```
`emacs/bjolang-dape.el` debugs a program with `dape` and
[netcoredbg](https://github.com/Samsung/netcoredbg/releases):
```elisp
(load "/home/linis/Programmering/BjolangLsp/emacs/bjolang-dape.el")
```
`M-x dape RET bjolang RET` in a file with a `main` builds it with `-d` and
runs it under the debugger. Breakpoints in the `.bjo` file bind, stepping
goes by its lines, and the call stack names them. The locals are the
generated C#'s, compiler temporaries included, and values show as their C#
types, which expand into their fields.
With eglot instead:
```elisp