Writing to the serial port crashes my application

[asthana]

Debug Trace leads me to below mentioned call
// return write(data.constData(), data.size());
mostly looks like the QByteArray issue. This issue happens 3 out of 5 times

Qt Version used Qt 5.3.0 MinGW 32bit

Any solution to this?? Thanks!

[VRonin]

@asthana said in Writing to the serial port crashes my application:

mostly looks like the QByteArray issue

Then try return write(data); instead. No need to pass QByteArray internals

[mrjj]

Hi and welcome to the forums.
You can try to upgrade to a newer version of Qt and see if it was fixed.

[asthana]

@VRonin Hi,
this is what the code i use
int size = mSerialManager->controlPort->write(data);

but on crash it goes to that line what I mentioned

[aha_1980]

@asthana

You need to check that mSerialManager and controlPort are valid pointers.

[mrjj]

@asthana
If you place a breakpoint and inspect the pointers.
They are both valid ?
mSerialManager / controlPort
?

[asthana]

@mrjj
Hi,
yeah i always check for that whether that port is null or not open
if( mSerialManager->controlPort->isOpen())
{
// code
}

[jsulm]

@asthana It's not about checking whether it is open or not. It is about checking the pointers before dereferencing them - dereferencing an invalid pointers crashes application.

[asthana]

@jsulm
yeah, I check for the pointer being valid and not null by using below code , open was just another check that I recently introduced...
if( mSerialManager->controlPort != NULL)
{
QByteArray data = Datamanager::getInstance()->getItemFromOutQueueCtrl();
int size = mSerialManager->controlPort->write(data);
}

[jsulm]

@asthana said in Writing to the serial port crashes my application:

int size = mSerialManager->controlPort->write(data);

Does it crash at this line?

[asthana]

exactly, as per debug trace it goes to the qt internal function call i.e
inline qint64 write(const QByteArray &data)
{ return write(data.constData(), data.size()); } in QIODevice.h and segmentation fault.
and checked the size of data as well its never zero.

[hskoglund]

Hi, I'm guessing that the QByteArray is torned down before all the bytes are transmitted, you could try to use a waitForBytesWritten() before the destructor of the QByteArray:

if( mSerialManager->controlPort != NULL)
{
    QByteArray data = Datamanager::getInstance()->getItemFromOutQueueCtrl();
    int size = mSerialManager->controlPort->write(data);
    mSerialManager->controlPort->waitForBytesWritten(-1);
}

or you could turn the QByteArray into a static one:

if( mSerialManager->controlPort != NULL)
{
    static QByteArray data = Datamanager::getInstance()->getItemFromOutQueueCtrl();
    int size = mSerialManager->controlPort->write(data);
}

[Christian Ehrlicher]

@asthana said in Writing to the serial port crashes my application:

if( mSerialManager->controlPort != NULL)

And where do you check for mSerialManager != nullptr? Or is it guaranteed that it can never be nullptr? And is controlPort really correctly initialized and not a dangling pointer?

[asthana]

@hskoglund
"mSerialManager->controlPort->waitForBytesWritten(-1);" actually slows down the application and since I am communication it to User Interface for display , the screen hangs and don't show any activity for sometime. I also tried giving a delay through this
i.e "waitForBytesWritten(20)" this works fine in terms of screen updates but still it crashes.

[asthana]

Debug Trace

Function: QIODevice::write(QByteArray const&)
0x4a3bc1 <+0x0025> mov %ebx,0x4(%esp)
0x4a3bc5 <+0x0029> mov %esi,0x8(%esp)
0x4a3bc9 <+0x002d> mov %eax,(%esp)
0x4a3bcc <+0x0030> mov %edx,%ecx
0x4a3bce <+0x0032> mov 0x544914,%eax
0x4a3bd3 <+0x0037> call *%eax
0x4a3bd5 <+0x0039> sub $0xc,%esp
0x4a3bd8 <+0x003c> lea -0x8(%ebp),%esp
0x4a3bdb <+0x003f> pop %ebx
0x4a3bdc <+0x0040> pop %esi
0x4a3bdd <+0x0041> pop %ebp
0x4a3bde <+0x0042> ret $0x4
Function: _ZN9QIODevice5writeERK10QByteArray
0x4a3be1 <+0x0045> nop
0x4a3be2 <+0x0046> nop
0x4a3be3 <+0x0047> nop

Please find the attched screenshot for the same

[aha_1980]

@asthana I don't think the QByteArray is the problem.

Please rather check @Christian-Ehrlicher's suggestion:

And where do you check for mSerialManager != nullptr? Or is it guaranteed that it can never be nullptr? And is controlPort really correctly initialized and not a dangling pointer?

That seems much more a possible cause for your problem.

Regards

[kuzulis]

I assume that you use a multiple threads (as I can see from your screenshoot with the 'Worker' class). If so, then you do it wrong... It is my assumption.

[J.Hilk]

@aha_1980
actually it can be,
from the looks of it, the serial port is threaded ( I take this from the naming of the class and the thread count)

And from the looks of it, Datamanager::getInstance()->getItemFromOutQueueCtrl(); may very well become invalid during the write process. As it seams to be a singleton and may be accessed by different threads?
One shouldn't do that, but it won't result in a compiler error.

[asthana]

@kuzulis
Yeah, there are two threads that read and write to the port, so to check on that I stopped sending any data from User Interface(UI) that my application was reading and only write the data to the port which is sent to UI .
But still the problem is there.

[kuzulis]

@asthana ,

Just read about the right way using the threads. You should to create the QSP instance and to call its methods only from the same thread.

E.g. if your worker was created in context of thread #2, then Worker::writeToControlPort() should be called too from the context of thread #2. Check the right thread id, just use QThread::currentThreadId() in ctor of Worker and inside of Worker::writeToControlPort() to see that this ID same.

PS: Read documentation, it is a main advice to you, before asking on a forum!!! It is simple...