English | English
German | Deutsch
Indonesian | Indonesia
Italian | Italiano
Spanish | Español
Turkish | Türkçe
32.2.1. General information
Debugger is a tool you can use to easily develop and debug modules in 1C:Enterprise. With Debugger, you can do the following:
- Debug module execution in both file mode and client/server modes and background jobs.
- Execute modules step-by-step.
- Set breakpoints.
- Interrupt and resume module execution.
- Debug multiple modules at the same time.
- Calculate expressions for variable status analysis.
- Change variable values during the debugging process.
- View the call stack of procedures and functions.
- Interrupt upon errors.
- Edit the module during the debugging process.
You can debug using two different protocols: over TCP/IP and HTTP. The capabilities provided by both debug protocols are fairly close. The following text applies equally to both protocols, unless any particular features or limitations explicitly specified.
The Debugger involves a debug item. Debug item is the context of 1C:Enterprise language with the following parameters:
- User name to run the code in 1C:Enterprise language.
- Debug item type.
- Session number used.
- Network name of the computer, on which the code in 1C:Enterprise language is executed (for the TCP/IP debug protocol).
- IP port number, through which the Debugger controls the debug item (for the TCP/IP debug protocol).
- Infobase name (for the HTTP debug protocol).
NOTE. If there are several workflows in the cluster in the client/server mode, and the session was reassigned to another workflow while debugging the code of the web client or server, then debugging becomes impossible.
Types of debug items include:
- COM connection. 1C:Enterprise language code executed through an external connection.
- HTTP service. 1C:Enterprise language code executed when calling HTTP service methods.
- Web service. 1C:Enterprise language code executed when calling web service methods.
- Standalone server (standalone mobile client). 1C:Enterprise language code executed on a mobile device, on the standalone server of the mobile client.
- Web client. 1C:Enterprise language code executed in the web client.
- Client (mobile application)*. 1C:Enterprise language code executed in the client application on a mobile device.
- Mobile client*. 1C:Enterprise language code executed in the mobile client.
- Server (mobile application). 1C:Enterprise language code executed on a mobile device, in the application on the mobile platform, on the server, or in file mode.
- Server (file mode). 1C:Enterprise language code executed on the server in file mode.
- Server. 1C:Enterprise language code executed on the server.
- Standard OData interface. 1C:Enterprise language code executed when you access an infobase via the standard OData interface.
- Thick client. 1C:Enterprise language code executed in the thick client.
- Thin client. 1C:Enterprise language code executed in the thin client.
- Background job (mobile application)*. 1C:Enterprise language code executed in a background job (in file mode) on a mobile device.
- Background job (file mode). 1C:Enterprise language code executed in a background job (in file mode).
- Background job. 1C:Enterprise language code executed in a background job.
Debug items marked with an asterisk "*" are used only if the HTTP debug protocol is applied.
During debugging, to indicate the system component addresses, both symbolic addresses (for example, pc-name) and IP addresses (for example, 192.168.1.1) can be used. 1C:Enterprise subsystems convert symbolic names to IP addresses, for example, to get the Debugger IP address, which is specified using a symbolic name. For this purpose, specialized services of the operating systems (DNS) are used. It is desirable that there are no ambiguities while resolving symbolic names.
Depending on the debug protocol used, 1C:Enterprise organizes the system components interactions in different ways. No matter what protocol is used, some ports of the protocol underlying the Debugger operations are used. If necessary for debugging ports are not allowed on the computer (the ports are “closed”), then debugging is unavailable. The following might happen:
- Longer startup time of the client application.
- 1C:Enterprise server workflow (rphost) slows down if the server is running in debug mode (‑debug key).
The following ports are used when running the Debugger:
- When you use the TCP/IP debug protocol: 1560-1591 (default). The range of ports can be changed. Ports are used on both Debugger side and the debug item side.
- When you use the HTTP debug protocol: the debug server port that is explicitly specified at startup. When working in the client/server mode, the debug server uses port 1550 (by default). When working in the file mode, the port is assigned explicitly or selected by the Designer from the port range 1560-1591 (by default). The range of ports can be changed. The port is used only on the computer where the debug server is running.
When using the TCP/ IP debug protocol, the port range can be changed using the system component settings or configuration files (debugcfg.xml). Ports used (single or range) must be enabled for use (“open”) on computers that are involved in the debugging process. For the TCP/IP debug protocol, these are all the computers involved in debugging, and for the HTTP debug protocol, this is the debug server computer.