After receiving a run-time exception from a macro, a fatal error message
appears and Developer Studio shuts down.
A code bug attempts to delete a run-time exception object twice.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in Visual Studio 6.0 Service Pack 3.
For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed
Steps to Reproduce Behavior
First save and close all projects and files. Then create a macro that will
generate a run-time exception as follows:
- On the Tools menu, click Macro.
- In the Macro dialog box, type TestMacro in the Macro Name edit box.
- Click Edit.
- When the Add Macro dialog box appears, click OK.
- The current .dsm macro file opens. The cursor is positioned in the
body of the TestMacro procedure. Type ActiveProject = 1 there.
- On the File menu, click Save.
To execute the macro:
- On the Tools menu, click Macro. A message might appear asking if you want to reload macros. Click Yes.
- Select TestMacro in the Macro Name list, and click Run.
- A macro exception appears. Click No.
- Repeat steps one through four until a fatal error occurs.
Article ID: 193478 - Last Review: August 11, 2005 - Revision: 1.2
- Microsoft Visual Studio 6.0 Enterprise Edition
- Microsoft Visual Studio 97 Service Pack 3
- Microsoft Visual C++ 5.0 Enterprise Edition
- Microsoft Visual C++ 6.0 Enterprise Edition
- Microsoft Visual C++ 5.0 Professional Edition
- Microsoft Visual C++ 6.0 Professional Edition
- Microsoft Visual C++, 32-bit Learning Edition 6.0
- Microsoft Visual InterDev 1.0 Standard Edition
- Microsoft Visual J++ 1.0 Standard Edition
- Microsoft Visual J++ 1.1 Standard Edition
|kbbug kbfix kbide kbvc600fix kbdevstudio kbdsstools kbvs600sp3fix KB193478|