SocketCANd: fix memory leak: string can be accessed after object destruction
This commit is contained in:
@@ -219,8 +219,8 @@ void SocketCANd::connectDevice()
|
|||||||
void SocketCANd::deviceConnected(int busNum)
|
void SocketCANd::deviceConnected(int busNum)
|
||||||
{
|
{
|
||||||
sendDebug("Opening CAN on Kayak Device!");
|
sendDebug("Opening CAN on Kayak Device!");
|
||||||
const char* openCanCmd = ("< open " + hostCanIDs[busNum] + " >").toStdString().c_str();
|
QString openCanCmd("< open " % hostCanIDs[busNum] % " >");
|
||||||
sendStringToTCP(openCanCmd, busNum);
|
sendStringToTCP(openCanCmd.toUtf8().data(), busNum);
|
||||||
|
|
||||||
QCoreApplication::processEvents();
|
QCoreApplication::processEvents();
|
||||||
}
|
}
|
||||||
@@ -383,8 +383,6 @@ void SocketCANd::procRXData(QString data, int busNum)
|
|||||||
mTimer.stop();
|
mTimer.stop();
|
||||||
mTimer.start();
|
mTimer.start();
|
||||||
}
|
}
|
||||||
QByteArray output;
|
|
||||||
|
|
||||||
switch (rx_state.at(busNum))
|
switch (rx_state.at(busNum))
|
||||||
{
|
{
|
||||||
case IDLE:
|
case IDLE:
|
||||||
|
|||||||
Reference in New Issue
Block a user