dbgshm does not allow creation in a separate console about diagnostics

[jkotas]

cc @mikem8361

[mikem8361]

I was trying to abstract CreateProcess to only the options that are supported across all platforms. Creating a new console on Linux and OS X would be difficult to support. I realize now it should be exposed for Windows but ignored on the other platforms.

It would have to be implemented as CreateProcess2 with the flags exposed. unless you are suggesting that we always create a new console on Windows with the existing API? That would probably be a breaking change.

[danwalmsley]

@mikem8361 hey, I think would be nice to have a CreateProcess2 and just ignore those flags on Mac / Linux.

[danwalmsley]

@mikem8361 i found that when i am debugging my debugger under visual studio no extra window is created, however when I run the application normally it actually creates a seperate window, does that sound familiar to you?

Also what is the recommended way to determine the path to dbgshm.dll?

[mikem8361]

Visual studio probably isn’t using dbgshim’s CreateProcessForLaunch and using CreateProcess directly allowing them to control the target process’s console window. This is ok if the SUSPEND flag is passed. The dbgshim API is a relatively new and VS never got around to using it. A workaround for this issue is to call CreateProcess directly. This is easy on Windows, but not on our other platforms (hence the reason for the dbgshim API). Dbgshim.dll is meant to be packaged with the debugger so it can install it as part of the debugger binaries. This is what VS does.