Version: 1.6.1 (using Devel) Compiler: visual studio 2005 OS: MS Windows Installed from: Compiled sources When I use tbytevector::replace function to processing "unsynchronization" flag, it can be "Out of bound" situation. For example, vector elements are looks that...(Hex data) 4D 43 44 49 00 00 00 3C 00 03 00 00 00 36 00 32 01 05 ......................................... ....................................FF 00 FF 00 while state run two times in tbytevector::replace ByteVector &ByteVector::replace(const ByteVector &pattern, const ByteVector &with) { if(pattern.size() == 0 || pattern.size() > size()) return *this; const int patternSize = pattern.size(); const int withSize = with.size(); int offset = find(pattern); while(offset >= 0) { const int originalSize = size(); if(withSize > patternSize) resize(originalSize + withSize - patternSize); //memcpy occurs "out of bound" exception in running second time //When occur exception, each values are // offset = 57 // originalSize = 59 // withSize = 1 // patternSize = 2 // so "offset + patternSize" be same originalSize // and "originalSize - offset - patternSize" = 0 if(patternSize != withSize) ::memcpy(data() + offset + withSize, mid(offset + patternSize).data(), originalSize - offset - patternSize); if(withSize < patternSize) resize(originalSize + withSize - patternSize); ::memcpy(data() + offset, with.data(), withSize); offset = find(pattern, offset + withSize); } return *this; }
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!