Application crash when connecting to Tektronix MDO3000 series scope

[rezafouladian]

When attempting to connect to a likely unsupported Tektronix Oscilloscope over LAN, rather than failing gracefully the application crashes after freezing for several seconds.

While it's expected that the scope does not support this command, it shouldn't bring the whole application down.

Connecting to SCPI device at 192.168.0.232:4000
[SCPISocketTransport::SendCommand] [192.168.0.232] Sending *IDN?
[SCPISocketTransport::ReadReply] [192.168.0.232] Got TEKTRONIX,MDO3104,P27,CF:91.1CT FV:v1.30
[SCPISocketTransport::SendCommand]     [192.168.0.232] Sending *CLS
[SCPISocketTransport::SendCommand]     [192.168.0.232] Sending *CLS
[SCPISocketTransport::SendCommand]     [192.168.0.232] Sending *IDN?
[SCPISocketTransport::ReadReply]     [192.168.0.232] Got TEKTRONIX,MDO3104,P27,CF:91.1CT FV:v1.30
[SCPISocketTransport::SendCommand]     [192.168.0.232] Sending HOR:MODE:RECO?
    Warning: Socket read timed out
[SCPISocketTransport::ReadReply]     [192.168.0.232] Got 
[SCPISocketTransport::SendCommand]     [192.168.0.232] Sending *IDN?
    Warning: Socket read timed out
[SCPISocketTransport::ReadReply]     [192.168.0.232] Got 
[SCPISocketTransport::SendCommand]     [192.168.0.232] Sending *IDN?
[SCPISocketTransport::ReadReply]     [192.168.0.232] Got TEKTRONIX,MDO3104,P27,CF:91.1CT FV:v1.30
[SCPISocketTransport::SendCommand]     [192.168.0.232] Sending *IDN?
[SCPISocketTransport::ReadReply]     [192.168.0.232] Got TEKTRONIX,MDO3104,P27,CF:91.1CT FV:v1.30
[SCPISocketTransport::SendCommand]     [192.168.0.232] Sending HOR:MODE:RECO?
    Warning: Socket read timed out
[SCPISocketTransport::ReadReply]     [192.168.0.232] Got 
[SCPISocketTransport::SendCommand]     [192.168.0.232] Sending HOR:MODE:RECO?
    Warning: Socket read timed out
[SCPISocketTransport::ReadReply]     [192.168.0.232] Got 
    ERROR: SCPI resync failed, firmware is probably in a bad state. Try rebooting the scope.
libc++abi: terminating due to uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument

Process finished with exit code 134 (interrupted by signal 6:SIGABRT)

System Info:
macOS Tahoe 26.2 - Apple Silicon
Tektronix MDO3104
Socket Server: Enabled
Protocol: None