PROIV Web Developer does not stop on break points

My break point is on a comment line.

For the debugger to stop on a line, the line must contain at least one statement. Lines that only contain comments do not contain statements. Try moving the break point to a line containing a statement.

My break point is on a line containing a single brace.

For the debugger to stop on a line, the line must contain at least one statement. Lines that only contain a single brace do not contain statements. Try moving the break point to a line containing a statement.

My break point is in a file that has been obfuscated.

If a file is obfuscated (compiled) the source page you are viewing within PROIV Web Developer is not actually run. Instead, the obfuscated file is run. This means the break point is never really reached. To debug such a page, you need to remove (or move) the obfuscated page so the "real" page is executed.

The obfuscated file has the same file name as the html file but with the .obv extension. If there is not a equivalent .html (or .htm) file, you do not have the source and you cannot debug the page.

My break point is in a library or fragment file.

Library and Fragment files can be called by many pages. To prevent all these pages from breaking when they call use a library or fragment, Active Web only processes break points if the calling file also contains break points.

Ensure the calling file contains at least one break point.

I am already debugging another file.

If you are already debugging another file, other files browsed will not stop on break points. You must first complete your current debug file by either turning the debugger off then on, by completing the page or by Playing another file.

To establish if you are currently debugging a file, examine the Stack. If the first item indicates a pause location you are debugging a file, if it say "Nopause location" you are not.

Comment on this topic

Topic ID: 150164