BUG: GPF When Setting a Breakpoint on a Stored Procedure

• Microsoft Visual InterDev, version 6.0

SYMPTOMS

Setting a breakpoint anywhere will cause a general protection fault (GPF) if there are currently no stored procedures in your project but there once was one that had a breakpoint set which was not explicitly removed. You will also get a GPF trying to view your current list of breakpoints if the project connection has already been made.

Similarly, if there is a shortcut to a stored procedure, but there are no longer any stored procedures in your project, following that shortcut will cause a GPF.

CAUSE

When enumerating breakpoints or tasks, the list of stored procedures is retrieved. When this list is empty, the code will cause a GPF.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

1. Add a stored procedure to your project.



2. Set a breakpoint in that stored procedure.



3. Remove all stored procedures.



4. Open an .htm or .asp page.



5. Set a breakpoint.

1. Add a stored procedure to your project.



2. Set a task in that stored procedure.



3. Remove all stored procedures.



4. Go to the task list and double-click the task.

Additional query words:

Keywords          : kbVisID600bug kbGrpASP kbIDEProject 
Version           : WINDOWS:6.0
Platform          : WINDOWS 
Issue type        : kbbug 

Last Reviewed: May 13, 1999