Knowledge Base

BUG: GPF When Setting a Breakpoint on a Stored Procedure

Article ID: 190756

Article Last Modified on 3/7/2005

Microsoft Visual InterDev 6.0 Standard Edition

This article was previously published under Q190756

SYMPTOMS

If your project formerly contained a stored procedure that had a breakpoint set, and the breakpoint set was not explicitly removed, setting a breakpoint anywhere may cause a general protection fault (GPF) if your project currently contains no stored procedures. You may also receive a GPF when you attempt 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 causes a GPF.

CAUSE

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

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are 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

Add a stored procedure to your project.
Set a breakpoint in the stored procedure.
Remove all stored procedures.
Open an .htm or .asp page.
Set a breakpoint.

You receive a GPF.

-or-

Add a stored procedure to your project.
Set a task in the stored procedure.
Remove all stored procedures.
Go to the task list and double-click the task.

You receive a GPF.

Keywords: kbbug kbdatabase kbpending kbideproject KB190756