KNOWLEDGE BASE
Log In    |    Knowledge Base    |    4D Home
Tech Tip: New v14 formatting of Debug Log
PRODUCT: 4D | VERSION: 14.x | PLATFORM: Mac & Win
Published On: October 5, 2015

In v14, the debug log contains the same information in interpreted and compiled mode (except for method parameters).

When the new tabulated format is used (see SET DATABASE PARAMETER (34) paragraph) the colums contain :

[1] sequence number (unique). Exemple: 123
[2] time stamp formated hh:mm:ss:ms. Exmple: 14:15:56:123 (see note below)
[3] 4D Process ID. Ex : 1
[4] 4D Unique Process ID. Ex : 18
[5] Deepness / depth of calling stack. Exemple 2
[6] ID of 4D command or 4D Method or plugin command number. Exemple 2 or mymeth or 12500,2
[7] parameters sent to the command or méthod. exemple : 42;hello
[8] Operation type
- 1: 4D Command
- 2: method
- 3: plugin message (ex: init)
- 4: plugin event (ex: redraw zone)
- 5: plugin command (ex: wr execute menu)
- 6: plugin callback
[9] form event (exemple: on clicked)
[10] duration in microseconds : provided only when the operation ends, otherwise left empty

Note :
if it started more than 24hours ago. The number of days is prepended to the timestamp, separated with a '+' sign.

Example:
The 24 first hours the format is unchanged, like:
6 15:13:03:368 5 7 0 5 -6 0 7930247
10 days later:
6 10+15:13:03:368 5 7 0 5 -6 0 7930247

In most cases, each operation is represented by two lines in the log file:
- the start of the operation (with all the informations but without duration)
- the end of the operarion will contain the information described below :
[6] sequence number of the (starting) operation
[7] empty
[8] operation starting type (in negative)
[10] duration (in micro-seconds)