Feature: Remote Debugging Server Alternative

[wilsonNg007]

HI @svnscha ,

In an enterprise secured environment where dumps can only be remotely examined, and it's not allowed to connect to my remote windows debugger ( .server tcp:port=5005 just returns access denied). In this case, I wonder if there is another alternative for mcp-windbg to connect with my remote debugger? Thanks.

[svnscha]

@wilsonNg007 How do you connect remotely right
now? Do you use a special command line or connect remotely via the UI?

Have you checked the develop branch? There is a work in progress feature to operate within an actual WinDBG session.

[wilsonNg007]

@svnscha it's just connected remotely via the Windbg UI since the dump cannot be downloaded to local machine.

Regarding "work in progress feature to operate within an actual WinDBG session." --- is it working? If so, will it be able to work in my case?

[svnscha]

I think so. Your use case is a good one, will add some guidance on the README on how to achieve that with the upcoming version.

[wilsonNg007]

Thanks. will the instruction/prompt be different than what you have in REAMDE ("connect to tcp port ... server....") ?

[svnscha]

Yes, in the next version I am preparing switching to prompt files with slash commands which gives us more fine tuned control on how to open the session.

[wilsonNg007]

I was testing the develop branch. Looks like it's still using cdb.exe and the connection_string to do remote attach - is that expected?
The cdb initialization timed out, so it failed to create cdb session. Not sure if it's another security thing that is blocking from being connected using connection_string (that I mentioned originally).

[svnscha]

@wilsonNg007 How do you exactly connect? The dump is stored remotely on a different machine with a WinDbg session in .server mode and you remote connect there?

That should work with the open remote tool with the current released version. If not, please provide a little bit more context so I can test/simulate this.