Microsoft KB Archive/251029

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


Article ID: 251029

Article Last Modified on 5/29/2003



APPLIES TO

  • Microsoft Visual InterDev 6.0 Standard Edition, when used with:
    • Microsoft Windows NT 4.0
    • Microsoft Windows 2000 Standard Edition



This article was previously published under Q251029

SYMPTOMS

When you try to stop the Visual InterDev 6.0 debugger using the Stop button, Visual InterDev becomes unresponsive (hangs) for a long period of time (approximately 5 minutes). After the time-out, the Visual InterDev debugger stops and returns to normal state.

CAUSE

When you stop the Visual InterDev debugger using the Stop button, Visual InterDev installs a COM message filter. Occasionally, when the time spent on a call is too long, the call is cancelled. In COM/RPC on Windows NT 4.0, calls to release cannot be cancelled, which causes the delay in stopping the debugger.

RESOLUTION

To work around this problem, detach the debugger rather than using the Stop button:

From the Debug menu, select Detach All Processes.

REFERENCES

For additional information on debugging references, click the article number below to view the article in the Microsoft Knowledge Base:

244272 INFO: Visual InterDev 6.0 Debugging Resources



Additional query words: hang

Keywords: kbbug kbdebug kbprb KB251029