drmemory
drmemory copied to clipboard
Warning with Qt QSerialPort program
I get the following Dr. Memory error. This might be a bug in Qt, but looking at http://code.qt.io/cgit/qt/qtserialport.git/tree/src/serialport/qserialportinfo_win.cpp I have not noticed anything particular.
Error #44: UNINITIALIZED READ: reading 0x02ff3e80-0x02ff3ea5 37 byte(s) within 0x02ff3e80-0x02ff3ea6
#0 system call NtWriteFile parameter #5
#1 KERNELBASE.dll!StrRStrIW +0x147 (0x76dd7c38 <KERNELBASE.dll+0x57c38>)
#2 Qt5SerialPortd.dll!QSerialPortInfo::productIdentifier+0x8ea0 (0x6508a829 <Qt5SerialPortd.dll+0xa829>)
#3 Qt5SerialPortd.dll!QSerialPortInfo::productIdentifier+0xa029 (0x6508b9b2 <Qt5SerialPortd.dll+0xb9b2>)
#4 Qt5SerialPortd.dll!QSerialPortInfo::productIdentifier+0x97bb (0x6508b144 <Qt5SerialPortd.dll+0xb144>)
#5 Qt5SerialPortd.dll!QSerialPortInfo::productIdentifier+0xa38f (0x6508bd18 <Qt5SerialPortd.dll+0xbd18>)
#6 Qt5Cored.dll!uppercasebase +0x3227d7 (0x63f2faaf <Qt5Cored.dll+0x33faaf>)
#7 Qt5Cored.dll!uppercasebase +0x315308 (0x63f225e0 <Qt5Cored.dll+0x3325e0>)
#8 Qt5Cored.dll!uppercasebase +0x314e09 (0x63f220e1 <Qt5Cored.dll+0x3320e1>)
#9 Qt5Cored.dll!uppercasebase +0x3f2fe1 (0x640002b9 <Qt5Cored.dll+0x4102b9>)
#10 Qt5Cored.dll!uppercasebase +0x32c846 (0x63f39b1e <Qt5Cored.dll+0x349b1e>)
#11 Qt5Cored.dll!uppercasebase +0x316913 (0x63f23beb <Qt5Cored.dll+0x333beb>)
#12 Qt5Cored.dll!uppercasebase +0x2d2834 (0x63edfb0c <Qt5Cored.dll+0x2efb0c>)
#13 Qt5Cored.dll!uppercasebase +0x2d3e9b (0x63ee1173 <Qt5Cored.dll+0x2f1173>)
#14 Qt5Cored.dll!uppercasebase +0x2d087b (0x63eddb53 <Qt5Cored.dll+0x2edb53>)
#15 Qt5Cored.dll!uppercasebase +0x2d1d04 (0x63edefdc <Qt5Cored.dll+0x2eefdc>)
#16 Qt5Cored.dll!uppercasebase +0x2da8a1 (0x63ee7b79 <Qt5Cored.dll+0x2f7b79>)
#17 Qt5Cored.dll!uppercasebase +0x3664ca (0x63f737a2 <Qt5Cored.dll+0x3837a2>)
#18 Qt5Cored.dll!uppercasebase +0x2d2834 (0x63edfb0c <Qt5Cored.dll+0x2efb0c>)
#19 Qt5Cored.dll!uppercasebase +0x2d3e9b (0x63ee1173 <Qt5Cored.dll+0x2f1173>)
Note: @0:00:40.820 in thread 9132
Any news on this?
Unfortunately Dr. Memory has been seriously understaffed for years now, but unless the error no longer occurs on the latest Dr. Memory version (is that the case?), we would prefer to keep it open on the off chance that resources are available to expand Dr. Memory support and address known false positives in the future.