Graphical Debugger error messages

A list of Graphical Debugger error messages. For messages that are not self-explanatory, additional information is provided.

Table 1. Graphical Debugger Error Messages
Number Description
GS-14100 Debug socket error: message

A connection error occurred while attaching to a process.

Check the provided connection information is correct. The message can provide a clue about what went wrong.

GS-14101 Failed to open debug port

The debug port couldn't be opened while attaching to a process.

Check the debug port provided (default: 4711) is available on the host running the process.

GS-14102 Display client is not a mobile client

A debug session on a mobile application was started while the current display client is not a mobile client.

Change the display client in the current configuration.

GS-14103 GMATOOLSDIR is not set

A debug session on an Androidâ„¢ application was started but GMATOOLSDIR is not set in the current configuration.

Set the GMATOOLSDIR environment variable in the current configuration. For further information, see Package and deploy rules.

GS-14104 GMITOOLSDIR is not set

A debug session on an iOS application was started but GMITOOLSDIR is not set in the current configuration.

Set the GMITOOLSDIR environment variable in the current configuration. For further information, see Package and deploy rules.

GS-14105 Failed to launch start script

A debug session on a mobile application was started but the current configuration startup script couldn't be launched.

Check the GMATOOLSDIR or GMITOOLSDIR environment variable is correct in the current configuration. For further information, see Package and deploy rules.

GS-14106 Failed to forward port

A debug session on a mobile application was started but the startup script couldn't forward the debug port.

Check the debug port is available on the host running the process.