PC SOFT

WINDEV, WEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
This content comes from an automatic translation.
  • Overview
  • How to proceed?
  • Inserting a breakpoint
  • Disabling/Enabling a breakpoint
  • Deleting one or more breakpoints
  • Listing the breakpoints
  • Conditional breakpoint
  • Breakpoint without stop but saved in the debug trace
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
During a project test in the editor, the breakpoints are used to automatically start the debugger from a given line.
How to proceed?

Inserting a breakpoint

Several methods can be used to insert a breakpoint:
  • Click on the left of the line where the breakpoint must be inserted. The mouse cursor turns into a hand and the sign is displayed.
  • Under "Code", in the "Breakpoints" group, scroll down "Breakpoint" and select "Stopping point".
  • Press Ctrl + B.
  • Display the popup menu of bar for breakpoint management and select "Add a breakpoint".
    Popup menu of breakpoints
Remark: The breakpoints are taken into account during the application tests in the editor of WINDEV, WEBDEV or WINDEV Mobile. The breakpoints are ignored when using the executable.
Versions 18 and later

Disabling/Enabling a breakpoint

A disabled breakpoint is still present in the code editor but it is ignored when debugging the application (it becomes grayed). Several methods can be used to disable the breakpoint for the current line:
  • Under the "Code" section, in the "Breakpoints" group, scroll down "Breakpoint" and select "Deactivate breakpoint".
  • Press Ctrl + Shift + B.
  • Display the popup menu of bar for breakpoint management and select "Disable the breakpoint":
Remark: The breakpoint can be re-enabled at any time via "Enable the breakpoint".
New in version 18

Disabling/Enabling a breakpoint

A disabled breakpoint is still present in the code editor but it is ignored when debugging the application (it becomes grayed). Several methods can be used to disable the breakpoint for the current line:
  • Under the "Code" section, in the "Breakpoints" group, scroll down "Breakpoint" and select "Deactivate breakpoint".
  • Press Ctrl + Shift + B.
  • Display the popup menu of bar for breakpoint management and select "Disable the breakpoint":
Remark: The breakpoint can be re-enabled at any time via "Enable the breakpoint".

Disabling/Enabling a breakpoint

A disabled breakpoint is still present in the code editor but it is ignored when debugging the application (it becomes grayed). Several methods can be used to disable the breakpoint for the current line:
  • Under the "Code" section, in the "Breakpoints" group, scroll down "Breakpoint" and select "Deactivate breakpoint".
  • Press Ctrl + Shift + B.
  • Display the popup menu of bar for breakpoint management and select "Disable the breakpoint":
Remark: The breakpoint can be re-enabled at any time via "Enable the breakpoint".

Deleting one or more breakpoints

Several methods can be used to delete a breakpoint:
  • In the code editor, click the breakpoint. The mouse cursor turns into a hand and the sign is displayed.
  • Under "Code", in the "Breakpoints" group, scroll down "Breakpoint" and select:
    • "Delete the breakpoint" to delete the breakpoint from the current line.
    • "Remove all breakpoints" to remove all breakpoints.
  • In the debugger, click .
  • Versions 18 and later
    Display the popup menu of bar for breakpoint management:
    • select "Delete the breakpoint" to delete the breakpoint found on the current line.
    • select "Remove all breakpoints" to delete all breakpoints.
    New in version 18
    Display the popup menu of bar for breakpoint management:
    • select "Delete the breakpoint" to delete the breakpoint found on the current line.
    • select "Remove all breakpoints" to delete all breakpoints.
    Display the popup menu of bar for breakpoint management:
    • select "Delete the breakpoint" to delete the breakpoint found on the current line.
    • select "Remove all breakpoints" to delete all breakpoints.
Versions 16 and later

Listing the breakpoints

Several methods can be used to list the breakpoints found in the current project:
  • From the code editor: Under the "Code" tab, in the "Breakpoints" group, scroll down "Breakpoint" and select "List breakpoints".
  • In the debugger, click .
  • Versions 18 and later
    Display the popup menu of bar for breakpoint management and select "List the breakpoints".
    New in version 18
    Display the popup menu of bar for breakpoint management and select "List the breakpoints".
    Display the popup menu of bar for breakpoint management and select "List the breakpoints".
New in version 16

Listing the breakpoints

Several methods can be used to list the breakpoints found in the current project:
  • From the code editor: Under the "Code" tab, in the "Breakpoints" group, scroll down "Breakpoint" and select "List breakpoints".
  • In the debugger, click .
  • Versions 18 and later
    Display the popup menu of bar for breakpoint management and select "List the breakpoints".
    New in version 18
    Display the popup menu of bar for breakpoint management and select "List the breakpoints".
    Display the popup menu of bar for breakpoint management and select "List the breakpoints".

Listing the breakpoints

Several methods can be used to list the breakpoints found in the current project:
  • From the code editor: Under the "Code" tab, in the "Breakpoints" group, scroll down "Breakpoint" and select "List breakpoints".
  • In the debugger, click .
  • Versions 18 and later
    Display the popup menu of bar for breakpoint management and select "List the breakpoints".
    New in version 18
    Display the popup menu of bar for breakpoint management and select "List the breakpoints".
    Display the popup menu of bar for breakpoint management and select "List the breakpoints".
Versions 20 and later

Conditional breakpoint

When debugging a loop, it may be useful to trigger the debugger after a number of passages (after the 35th iteration for example). To implement a conditional breakpoint:
  1. Create a breakpoint (Inserting a breakpoint paragraph).
  2. Display the breakpoint properties:
    • via the code editor: Under "Code", in the "Breakpoints" group, scroll down "Breakpoint" and select "Stopping point properties".
    • via the popup menu of breakpoint: Display the popup menu of bar for breakpoint management and select "Breakpoint properties".
  3. In the window that is displayed, in the "Conditions" area, specify the conditions for taking the breakpoint into account:
    • Always (default value): The breakpoint will not be conditional and it will always be taken into account.
    • When the number of passages on the breakpoint is: Used to make the breakpoint conditional. To do so, select a condition and the requested number of passages.
  • When the expression below is true: Used to make the breakpoint conditional. Simply enter the condition directly in the "If" field..
  1. Validate. The conditional breakpoint is displayed in the editor ( ).
New in version 20

Conditional breakpoint

When debugging a loop, it may be useful to trigger the debugger after a number of passages (after the 35th iteration for example). To implement a conditional breakpoint:
  1. Create a breakpoint (Inserting a breakpoint paragraph).
  2. Display the breakpoint properties:
    • via the code editor: Under "Code", in the "Breakpoints" group, scroll down "Breakpoint" and select "Stopping point properties".
    • via the popup menu of breakpoint: Display the popup menu of bar for breakpoint management and select "Breakpoint properties".
  3. In the window that is displayed, in the "Conditions" area, specify the conditions for taking the breakpoint into account:
    • Always (default value): The breakpoint will not be conditional and it will always be taken into account.
    • When the number of passages on the breakpoint is: Used to make the breakpoint conditional. To do so, select a condition and the requested number of passages.
  • When the expression below is true: Used to make the breakpoint conditional. Simply enter the condition directly in the "If" field..
  1. Validate. The conditional breakpoint is displayed in the editor ( ).

Conditional breakpoint

When debugging a loop, it may be useful to trigger the debugger after a number of passages (after the 35th iteration for example). To implement a conditional breakpoint:
  1. Create a breakpoint (Inserting a breakpoint paragraph).
  2. Display the breakpoint properties:
    • via the code editor: Under "Code", in the "Breakpoints" group, scroll down "Breakpoint" and select "Stopping point properties".
    • via the popup menu of breakpoint: Display the popup menu of bar for breakpoint management and select "Breakpoint properties".
  3. In the window that is displayed, in the "Conditions" area, specify the conditions for taking the breakpoint into account:
    • Always (default value): The breakpoint will not be conditional and it will always be taken into account.
    • When the number of passages on the breakpoint is: Used to make the breakpoint conditional. To do so, select a condition and the requested number of passages.
  • When the expression below is true: Used to make the breakpoint conditional. Simply enter the condition directly in the "If" field..
  1. Validate. The conditional breakpoint is displayed in the editor ( ).
Versions 23 and later

Breakpoint without stop but saved in the debug trace

In some cases, when debugging an application, it is useful to know the code line on which the process passed but without stopping in the debugger. In this case, a single information must be displayed in the trace window.
To implement this feature:
  1. Create a breakpoint (Inserting a breakpoint paragraph).
  2. Display the breakpoint properties:
    • via the code editor: Under "Code", in the "Breakpoints" group, scroll down "Breakpoint" and select "Stopping point properties".
    • via the popup menu of breakpoint: Display the popup menu of bar for breakpoint management and select "Breakpoint properties".
  3. In the window that is displayed, in the "Actions" area, specify the action to perform during the passage by the breakpoint (these actions can be combined):
    • Interrupt execution (default value): the breakpoint interrupts the execution ans starts the debugger on the current code line.
    • Add a message into the debugger trace: the passage by the breakpoint adds the message specified in the "Trace of debugger" pane.
      Remark: If no message is specified, the name of current process is displayed in the "Trace of debugger" pane.
    Remark: If the two actions are unchecked, the breakpoint is automatically disabled.
  4. Validate. The icon found before the breakpoint indicates that it includes specific properties.
New in version 23

Breakpoint without stop but saved in the debug trace

In some cases, when debugging an application, it is useful to know the code line on which the process passed but without stopping in the debugger. In this case, a single information must be displayed in the trace window.
To implement this feature:
  1. Create a breakpoint (Inserting a breakpoint paragraph).
  2. Display the breakpoint properties:
    • via the code editor: Under "Code", in the "Breakpoints" group, scroll down "Breakpoint" and select "Stopping point properties".
    • via the popup menu of breakpoint: Display the popup menu of bar for breakpoint management and select "Breakpoint properties".
  3. In the window that is displayed, in the "Actions" area, specify the action to perform during the passage by the breakpoint (these actions can be combined):
    • Interrupt execution (default value): the breakpoint interrupts the execution ans starts the debugger on the current code line.
    • Add a message into the debugger trace: the passage by the breakpoint adds the message specified in the "Trace of debugger" pane.
      Remark: If no message is specified, the name of current process is displayed in the "Trace of debugger" pane.
    Remark: If the two actions are unchecked, the breakpoint is automatically disabled.
  4. Validate. The icon found before the breakpoint indicates that it includes specific properties.

Breakpoint without stop but saved in the debug trace

In some cases, when debugging an application, it is useful to know the code line on which the process passed but without stopping in the debugger. In this case, a single information must be displayed in the trace window.
To implement this feature:
  1. Create a breakpoint (Inserting a breakpoint paragraph).
  2. Display the breakpoint properties:
    • via the code editor: Under "Code", in the "Breakpoints" group, scroll down "Breakpoint" and select "Stopping point properties".
    • via the popup menu of breakpoint: Display the popup menu of bar for breakpoint management and select "Breakpoint properties".
  3. In the window that is displayed, in the "Actions" area, specify the action to perform during the passage by the breakpoint (these actions can be combined):
    • Interrupt execution (default value): the breakpoint interrupts the execution ans starts the debugger on the current code line.
    • Add a message into the debugger trace: the passage by the breakpoint adds the message specified in the "Trace of debugger" pane.
      Remark: If no message is specified, the name of current process is displayed in the "Trace of debugger" pane.
    Remark: If the two actions are unchecked, the breakpoint is automatically disabled.
  4. Validate. The icon found before the breakpoint indicates that it includes specific properties.
See also
Minimum version required
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment