This doesn’t look like a message produced by VisualGDB. Our latest mbed package is based on mbed 5.6.3, so most likely the message comes from some missing configuration variables. We would advise trying to locate the code producing the message and adjusting it accordingly.