FIX: Run-time Macro Errors Cause Developer Studio to Crash

ID: Q193478

The information in this article applies to:

SYMPTOMS

After receiving a run-time exception from a macro, a fatal error message appears and Developer Studio shuts down.


CAUSE

A code bug attempts to delete a run-time exception object twice.


STATUS

Microsoft has confirmed this to be a bug in the Microsoft products 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:

Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why

Q194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed


MORE INFORMATION

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:
  1. On the Tools menu, click Macro.


  2. In the Macro dialog box, type TestMacro in the Macro Name edit box.


  3. Click Edit.


  4. When the Add Macro dialog box appears, click OK.


  5. The current .dsm macro file opens. The cursor is positioned in the body of the TestMacro procedure. Type ActiveProject = 1 there.


  6. On the File menu, click Save.


To execute the macro:
  1. On the Tools menu, click Macro. A message might appear asking if you want to reload macros. Click Yes.


  2. Select TestMacro in the Macro Name list, and click Run.


  3. A macro exception appears. Click No.


  4. Repeat steps one through four until a fatal error occurs.


Additional query words: 


Keywords          : kbservicepack kbide kbVC500bug kbVC600bug kbVisID100bug kbVJ100bug kbVJ110bug kbVS97bug kbVS600bug kbDevStudio kbVS600sp2 kbVS600SP1 kbVS600sp3fix 
Version           : WINDOWS:1.0,1.1,6.0,97; winnt:5.0,6.0
Platform          : WINDOWS winnt 
Issue type        : kbbug

Last Reviewed: May 19, 1999