PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • Configuring the remote computer
  • Configuring WDDebug
  • Running and debugging the executable on a remote computer
  • Debugging an executable that is already run on a remote computer
  • Starting the debugger and stopping the test
  • Starting the debugger
  • Stopping the test
  • Advanced setting of debugging ports
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
Several methods can be used to run the test of a project and to debug it on the development computer (see Running the test of a WINDEV executable on the development computer and debugging it). However, in some cases, you may have to debug on the end-user computer (connected by network or by Internet).
From your office in London, you have the ability to debug an application that is run in Taiwan. The debug operation is performed without having to go anywhere, directly on the user configuration.
Two features are available:
  • Running and debugging the executable on a remote computer
  • Debugging an application that is currently run on a remote computer.
For these two features, a specific configuration is required for the remote computer.
Note: To debug a WINDEV application remotely, the WINDEV application must include the wdxxxcpl.dll library in its framework.
Configuring the remote computer
To debug a WINDEV application on a remote computer, you must:
  • open the ports 27270 and 27280 if a firewall is used. Indeed, the communication between the development computer and the end-user computer is done via sockets. These ports can be customized. See "Advanced setting of debugging ports" in this page.
  • install and start WDDebug on the end-user computer. WDDebug can be supplied with the application (application available in the additional modules when creating the setup).
    Note: on a 64-bit computer, the WDDebug64 application must be started.
Notes:
  • WDDebug (32-bit version and 64-bit version) is an application that can be supplied separately. A setup pack is available in the "Install\WDDebug" sub-directory of the setup directory of WINDEV (WX230PACKWDDEBUG.exe). Caution: WDDebug can only be used on the computers running Windows 2000 or later.
  • On a TSE session, WDDebug does not list the executables of the other sessions available on the computer. You cannot trace an executable started on the console from a TSE session on the computer.
  • To start WDDebug on the development computer:
    • the 32-bit version (WDDebug.exe) is available in the "\Programs" directory of the setup directory of WINDEV.
    • the 64-bit version (WDDebug64.exe) is available in the "\Programs\Framework\Win64x86" directory of the setup directory of WINDEV.
  • WDDebug64 must be run in "Administrator" mode if the executable to debug is in UAC mode.

Configuring WDDebug

To debug a WINDEV application on a remote computer, WDDebug must be configured by the end user:
  • "Allow the remote debugging for the applications and services currently run" must be checked in order to be able to debug an application (or a service) currently run. The list of WINDEV applications currently run is displayed. The application to debug must be selected from this list.
  • "Allow to start and to remotely debug an application" gives you the ability to remotely start and debug the specified application. In this case, the full name of the application as well as its command line must be specified (if it exists).
  • "Allow the application to be restarted" allows you to transfer the information regarding an application currently run into the parameters in order to allow the application to be started. Indeed, the developer may want to restart the application in order to reproduce the bug.
  • "Allow to start and debug a service remotely" gives you the ability to remotely start and debug the specified service.
Caution: You cannot debug several executables or services simultaneously on the same machine from several remote computers (for example, two developers who try to debug two different applications at the same time on the same remote computer).
Running and debugging the executable on a remote computer
To run and debug an executable on a remote computer:
  1. Open the relevant project in WINDEV.
  2. Contact the user in order to configure his computer.
  3. Select "Project .. Test mode .. Run and debug the executable on a remote computer".On the "Project" pane, in the "Test mode" group, expand "Test mode" and select "Start and debug the executable on a remote computer".
  4. In the window that is displayed, enter the name or IP address of the remote computer and click the "Refresh" button. The name of the application to debug is displayed. This name corresponds to the application specified by the end user.
  5. Validate.
  6. The application is started in debug mode on the user computer. The user can handle the application while you can follow the code run via the debugger (by including breakpoints in the sections of code where the problems occur).
Note: Therefore, the code of the current project in the editor and the code of the executable can become out-of-sync: the out-of-sync code is highlighted in pink during the debug operation.
Debugging an executable that is already run on a remote computer
To debug an executable that is already run on a remote computer:
  1. Open the relevant project in WINDEV.
  2. Contact the user in order to configure his computer.
  3. Select "Project .. Test mode .. Run and debug the executable on a remote computer".On the "Project" pane, in the "Test mode" group, expand "Test mode" and select "Start and debug the executable on a remote computer".
  4. In the window that is displayed, enter the name or IP address of the remote computer and click the "Refresh" button. The list of applications available on the remote computer is displayed.
  5. Select the requested application and validate.
  6. The application is in debugging mode.
Starting the debugger and stopping the test

Starting the debugger

To start the debugger while running the test of the executable, use the editor:
  • In the "Code" pane, "Debugger" option, click the icon shaped like a hand ( ).
  • A breakpoint can also be included in the code editor in front of the requested code line. The debugger will be automatically displayed when the corresponding line is run.

Stopping the test

Several methods can be used to stop the test:
  • 1st method: Close the application whose test is currently run. WINDEV displays the editor that was used at the beginning of test.
  • 2nd method: In the editor, stop the debugger ( or SHIFT + F5).
Advanced setting of debugging ports
If you do not want to use the debugging ports proposed by default, you have the ability to configure the debugging ports in the registry.
The ports must be configured on the development computer and on the debugging computer.
On the development computer: In the "HKEY_CURRENT_USER\SOFTWARE\PC SOFT\WINDEV\23.0\Common" registry, create the following "DWORD 32 Bits" value: "DBG_Port_COM". This value contains the number of the communication port on the server.
On the computer where the debug operation must be performed:
  1. Create the "HKEY_CURRENT_USER\SOFTWARE\PC SOFT\WDDEBUG\23.0" key if necessary.
  2. In the "HKEY_CURRENT_USER\SOFTWARE\PC SOFT\WDDEBUG\23.0" registry, create the following "DWORD 32 Bits" value: "DBG_Port_COM". This value contains the number of the communication port on the server. It must be identical to the value specified on the development computer.
  3. In the "HKEY_CURRENT_USER\SOFTWARE\PC SOFT\WDDEBUG\23.0" registry, create the following "DWORD 32 Bits" value: "DBG_Port_DBG". This value contains the number of the debugging port.
    This port must be allowed in the firewall of the client computer.
Note: These parameters are taken into account when starting WDDebug.
Minimum required version
  • Version 12
Comments
Click [Add] to post a comment