You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running PothosFlow v0.61 from the PPA on Ubuntu 18.04. I have a remote device running PothosUtil 0.7.0, built from source on a pi CM3. Both devices are on the same local LAN. When I add it to PothosFlow as remote device, it seems to connect and reports a Last Access time. If I double click to show System Info for the device, PothosFlow brings up a message box with "Exception: std::exception", then exits.
I attached the debugger to PothosFlow (without source) to the debugger and the call stack was:
1 kill
2 Poco:ProcessImpl::requestTerminationImpl(int)
3 ??
4 Poco::Net::TCPServerDispatcher::run()
5 Poco::pooledThread::run()
6 Poco::ThreadImpl::runnableEntry(void*)
7 start_thread
8 clone
If I launch it from the console, I see the following output after I exit the dialog:
2020-04-09 15:15:04 default: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
If that is not possible, in Qt 5 you must at least reimplement
QCoreApplication::notify() and catch all exceptions there.
I've tried various URIs (named, IPv4, etc), but all fail identically
All works fine from an adjacent Windows 10 box.
Sorry, its not much to go on.
The text was updated successfully, but these errors were encountered:
I'm running PothosFlow v0.61 from the PPA on Ubuntu 18.04. I have a remote device running PothosUtil 0.7.0, built from source on a pi CM3. Both devices are on the same local LAN. When I add it to PothosFlow as remote device, it seems to connect and reports a Last Access time. If I double click to show System Info for the device, PothosFlow brings up a message box with "Exception: std::exception", then exits.
I attached the debugger to PothosFlow (without source) to the debugger and the call stack was:
1 kill
2 Poco:ProcessImpl::requestTerminationImpl(int)
3 ??
4 Poco::Net::TCPServerDispatcher::run()
5 Poco::pooledThread::run()
6 Poco::ThreadImpl::runnableEntry(void*)
7 start_thread
8 clone
If I launch it from the console, I see the following output after I exit the dialog:
2020-04-09 15:15:04 default: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
If that is not possible, in Qt 5 you must at least reimplement
QCoreApplication::notify() and catch all exceptions there.
I've tried various URIs (named, IPv4, etc), but all fail identically
All works fine from an adjacent Windows 10 box.
Sorry, its not much to go on.
The text was updated successfully, but these errors were encountered: