search

microsoft / vscode-mono-debug

A simple VS Code debug adapter for mono
Other
159 stars 173 forks source link

Debugging for custom languages broken #10

Closed borgdylan closed 8 years ago

borgdylan commented 8 years ago

I was debugging my custom .NET language code using this extension (added the extension for the files in the MonoDebugSession white list). In the past this used to work but after updating to the latest insiders build this is no ;longer the case.

weinand commented 8 years ago

@borgdylan could you please be more specific: what exactly does not work for you? Setting breakpoints? Launching? On which platform? Which version of mono? Which version of VS Code?

borgdylan commented 8 years ago

To set breakpoints I had to hack the configuration file to include the language. What does not work is stopping on the breakpoints I set. I am on Linux using the latest insiders build of Code on the latest mono from github.

borgdylan commented 8 years ago

To be more clear I am using Code v. 0.10.12-insider. When I will be using the PC in question I will post the commit SHA of mono and the extension version as well.

borgdylan commented 8 years ago

Full version info: Code: 0.10.12-insider vscode-mono-debug: 0.10.18 mono: f6de55f55857e60684ca1b85445dfb80309b0d28

weinand commented 8 years ago

@borgdylan could you please provide reproducible steps for your problem? A test project on github would be ideal.

borgdylan commented 8 years ago

I am using custom compilers currently which does not make it easy to reproduce. I will try the mono command line debugger client and see if the issue arises from the mono debugger library being out of date in the code extension.

borgdylan commented 8 years ago

The sdb dependency on the extension is extremely out of date. It uses the May 2015 variant while the latest commits are dated January 2016.

borgdylan commented 8 years ago

A similar bug was fixed in the mono debugger libraries: https://github.com/mono/debugger-libs/commit/607c1dae16527b13377344b1f2ad2a221848e9d7

borgdylan commented 8 years ago

Fixed by renaming monoDebug.exe to mono-debug.exe