-
Kai Koehne authored
Actually wait for the 'Waiting for debugger on port ' ... message to appear in the application output before connecting, and also use the port specified there. Change-Id: Ib498e5306bc49f2f3d468353b1c5d1ea38a809e6 Reviewed-by:
Christian Kandeler <christian.kandeler@nokia.com>
Kai Koehne authoredActually wait for the 'Waiting for debugger on port ' ... message to appear in the application output before connecting, and also use the port specified there. Change-Id: Ib498e5306bc49f2f3d468353b1c5d1ea38a809e6 Reviewed-by:
Christian Kandeler <christian.kandeler@nokia.com>
qmljsdebugclientconstants.h 718 B
#ifndef QMLJSDEBUGCLIENTCONSTANTS_H
#define QMLJSDEBUGCLIENTCONSTANTS_H
namespace QmlJsDebugClient {
namespace Constants {
const char STR_WAITING_FOR_CONNECTION[] = "Waiting for connection ";
const char STR_ON_PORT_PATTERN[] = "on port (\\d+)";
const char STR_VIA_OST[] = "via OST";
const char STR_UNABLE_TO_LISTEN[] = "Unable to listen ";
const char STR_IGNORING_DEBUGGER[] = "Ignoring \"-qmljsdebugger=";
const char STR_IGNORING_DEBUGGER2[] = "Ignoring\"-qmljsdebugger="; // There is (was?) a bug in one of the error strings - safest to handle both
const char STR_CONNECTION_ESTABLISHED[] = "Connection established";
} // namespace Constants
} // namespace QmlJsDebugClient
#endif // QMLJSDEBUGCLIENTCONSTANTS_H