Difficult to tell without looking at the code what's going wrong.
I guess that because you're accessing a network some async signal is trying to access a part of memory that it shouldn't.
MOC files are produced by meta-object compiler.
as to the qt_metacall function, it's how it looks when object has no signals/slots defined, it's just a scaffolding and it's there beacuse Q_OBJECT macro was defined in the header file.
(ps please use [code] tags)
int StatusProcess
::qt_metacall(QMetaObject::Call _c,
int _id,
void **_a
) {
if (_id < 0)
return _id;
return _id;
}
int StatusProcess::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
{
_id = QProgressBar::qt_metacall(_c, _id, _a);
if (_id < 0)
return _id;
return _id;
}
To copy to clipboard, switch view to plain text mode
as soon as you define some signal or slot the function will start to grow and will look something like that:
int StatusProcess
::qt_metacall(QMetaObject::Call _c,
int _id,
void **_a
) {
if (_id < 0)
return _id;
switch (_id) {
case 0: someSignal(); break;
case 1: someSlot(); break;
default: ;
}
_id -= 2;
}
return _id;
}
int StatusProcess::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
{
_id = QProgressBar::qt_metacall(_c, _id, _a);
if (_id < 0)
return _id;
if (_c == QMetaObject::InvokeMetaMethod) {
switch (_id) {
case 0: someSignal(); break;
case 1: someSlot(); break;
default: ;
}
_id -= 2;
}
return _id;
}
To copy to clipboard, switch view to plain text mode
Bookmarks