search

muhammadsammy / free-vscode-csharp

Free/Libre fork of the official C# extension for vscode
https://open-vsx.org/extension/muhammad-sammy/csharp
Other
138 stars 16 forks source link

Debugger stops working on release 2.45.25 #81

Open rafaeltuelho opened 2 weeks ago

rafaeltuelho commented 2 weeks ago

The debugger is not working anymore after upgrading to the latest release (2.45.25). I was not able to find/see any error msg as evidence to paste here. But the debugger doesn't work anymore.

muhammadsammy commented 2 weeks ago

Could you provide more info about your environment and scenario? I tested it on VSCodium for Linux and it works fine.

rafaeltuelho commented 2 weeks ago

Hi @muhammadsammy ! I am using it on a containerized environment using Eclipse Che. The VSCode runs on a RHEL based image (UBI9 with .NET 8 runtime/sdk).

Here is the repo I'm using to test it: https://github.com/rafaeltuelho/devspaces-dotnet-web-api-sample here is a quick recording. dotnet-vscode

orkunevran commented 1 week ago

Hi @muhammadsammy ! I am using it on a containerized environment using Eclipse Che. The VSCode runs on a RHEL based image (UBI9 with .NET 8 runtime/sdk).

Here is the repo I'm using to test it: https://github.com/rafaeltuelho/devspaces-dotnet-web-api-sample here is a quick recording. dotnet-vscode dotnet-vscode

We have confronted same issue and same error as "terminal will be reused by tasks press any key to close it" while we are trying to use debugger with version 2.45.25 with dotnet 7.0 and dotnet 6.0 at Openshift Devspaces (Eclipse Che).

After downgrading from 2.45.25 to 2.39.29, dubegger function works.

svor commented 1 week ago

Seems the problem with the environment. Netcoredbg used in 2.45.25 requires GLIBCXX_3.4.30:

/checode/remote/extensions/muhammad-sammy.csharp-2.45.25-universal/.debugger/netcoredbg/netcoredbg: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /checode/remote/extensions/muhammad-sammy.csharp-2.45.25-universal/.debugger/netcoredbg/netcoredbg)
rafaeltuelho commented 1 week ago

Tested using a Container image based on Fedora:42 and it works as Fedora provides new versions of the libstdc++ required by the new release of this extension.