Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugger class on Linux #38427

tmds opened this issue Jun 26, 2020 · 2 comments

Debugger class on Linux #38427

tmds opened this issue Jun 26, 2020 · 2 comments


Copy link

@tmds tmds commented Jun 26, 2020

When I call Debugger.Launch(/Debugger.Break) that doesn't do much on Linux.
I assume on Windows, this will launch Visual Studio?

Maybe it is possible to provide a hook so an IDE can be launched also on Linux, like VS Code?
For example, the method could launch a script that is found under /etc/dotnet/ and pass it the pid as an argument.
The script can launch the IDE and make it attach to the process.

cc @mikem8361 @DustinCampbell

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-Diagnostics-coreclr untriaged labels Jun 26, 2020
Copy link

@msftbot msftbot bot commented Jun 26, 2020

Tagging subscribers to this area: @tommcdon
Notify danmosemsft if you want to be subscribed.

Copy link

@Wraith2 Wraith2 commented Jun 27, 2020

It traces into

hr = g_pDebugInterface->LaunchDebuggerForUser(GetThread(), NULL, TRUE, TRUE);
and I assume that on windows various debuggers are registered and the watson/os takes the signal and allows the user to choose the deugger, it's certainly not hardcoded to VS.

@sdmaclea sdmaclea added this to Needs Triage in .NET Core Diagnostics via automation Jun 29, 2020
@sdmaclea sdmaclea added this to the Future milestone Jun 29, 2020
@sdmaclea sdmaclea added feature-request os-linux and removed untriaged labels Jun 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

4 participants