Skip to content
This repository has been archived by the owner on Aug 30, 2021. It is now read-only.

Trouble getting started #1

Open
germgerm opened this issue May 9, 2019 · 5 comments
Open

Trouble getting started #1

germgerm opened this issue May 9, 2019 · 5 comments
Labels
question Further information is requested

Comments

@germgerm
Copy link

germgerm commented May 9, 2019

Am interested in using/helping with this project.
After following the install directions, everything seems to be in place but when attempting to debug a simple console app, the console window is never displayed ( works if started without debugging ) and the program just exits. It looks like VSCodeDebuggerSession.OnDebugAdaptorRequestReceived is never being called to start up the console.
Monodevelop had a similar issue when using xfce-terminal. I am wondering that this is the same issue surfacing here. Can you tell what your test invironment is ? Are you getting a console up and running under debug
?

@lextm
Copy link
Collaborator

lextm commented May 9, 2019

If you want to see an external console, that's not supported right now. The Samsung debugger only accepts some settings,

  • "program"
  • "args"
  • "stopAtEntry" (not used by this extension)

https://github.com/Samsung/netcoredbg/blob/9d0608ff8f39ab6e0fbff448bdd8c485b56b2761/src/debug/netcoredbg/vscodeprotocol.cpp#L316

Visual Studio for Mac/MonoDevelop uses integrated terminal (an "Application Output" panel) to show you the console output instead.

@lextm lextm added the question Further information is requested label May 9, 2019
@germgerm
Copy link
Author

Thanks - are you getting any breakpoints to work ?

@lextm
Copy link
Collaborator

lextm commented May 10, 2019

What debugger are you using? The binaries from Samsung repo won't work, as they don't support the actual VSCode debugging protocol the way they should. You need to compile from my fork, as readme says.

@germgerm
Copy link
Author

I am using the debugger compiled from your repo as instructed.

@lextm
Copy link
Collaborator

lextm commented May 15, 2019

I won't be able to help, as I could not reproduce this on both Mac and Ubuntu. You might debug the code base further to see if you locate some hints.

BTW, "It looks like VSCodeDebuggerSession.OnDebugAdaptorRequestReceived is never being called to start up the console" is expected.

If you want to set some break points, you might consider,

  • DotNetCoreDebuggerSession.CreateLaunchRequest is called before launching the debugger.
  • Add an overriding method DotNetCoreDebuggerSession.OnGetProcesses as it is called right after the debugger launches the console application.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants