WTF? "debugger could not connect... Win32 error 5 Access is denied"

[vc6vc6]

I was able to successfully run several times a remote debug session
(i.e. start/stop debug server, including the debugged application).
This includes starting/stopping windbg with the -remote option (for
the client).

But all of a sudden, I cannot start windbg anymore. The server starts
and runs OK (using the same exact command), but when I start the
client (using the SAME EXACT windbg -remote command as before), it
issues an error message box:

"The debugger could not connect using com:port=1,baud=115200,channel=0
Win32 error 5 Access is denied"

What gives?

Please note: using "com:port=1,baud=115200,channel=0" ran successfully
numerious times before WinDbg started acting funny on me.

I am using WinDbg version 6.6.0007.5.

And I verified that the server is *not* in Secure mode.

Any idea why is that? Could that be a bug in WinDbg?

Thanks,
Victor

[vc6vc6]

OK - problem fixed. It turns out that the reason I was getting this
error was because there was a hung WinDbg session that somehow failed
to exit (although its window closed).

I just could think of the possibility that WinDbg, a tool that is
supposed to help me find a nasty bug that causes my application to
refuse to exit (due to a hung MsgWaitForMultipleObjects) - will have
the same exact bug... LOL.

Thanks!
Victor

[Don Burn]

The most likely answer is that another instance of windbg is already using
the com port. A weirder case would be another program using the port.

--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

"vc6vc6" <vc6...@gmail.com> wrote in message
news:1192649900.9...@i13g2000prf.googlegroups.com...

[vc6vc6]

On Oct 17, 3:47 pm, "Don Burn" <b...@stopspam.windrvr.com> wrote:
> The most likely answer is that another instance of windbg is already
> using the com port. A weirder case would be another program using
> the port.

Don, thanks. Yes - that's exactly what I discovered. It just didn't
occur to me that WinDbg could be running after actually being closed.
All is well now - and am faced with a new challenge (see new posting
regarding !stacks).

Thanks,
Victor