==2800== Memcheck, a memory error detector
==2800== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==2800== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==2800== Command: ./concentration
==2800==
vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF2 0xB9 0x1 0x0 0x0 0x0
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==2800== valgrind: Unrecognised instruction at address 0x5cd8320.
==2800==    at 0x5CD8320: ??? (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5CD8F08: ??? (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5CD9998: QRandomGenerator::_fillRange(void*, void*) (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5D37BEB: ??? (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5D38585: QHashData::detach_helper(void (*)(QHashData::Node*, void*), void (*)(QHashData::Node*), int, int) (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5D53C62: ??? (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5D54094: QRegExp::QRegExp(QString const&, Qt::CaseSensitivity, QRegExp::PatternSyntax) (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5DE3C6B: ??? (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5DE477B: QDirIterator::QDirIterator(QString const&, QStringList const&, QFlags<QDir::Filter>, QFlags<QDirIterator::IteratorFlag>) (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5DDDAAB: QDir::entryList(QStringList const&, QFlags<QDir::Filter>, QFlags<QDir::SortFlag>) const (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5DDE11E: QDir::entryList(QFlags<QDir::Filter>, QFlags<QDir::SortFlag>) const (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5EBE259: QFactoryLoader::update() (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800== Your program just tried to execute an instruction that Valgrind
==2800== did not recognise.  There are two possible reasons for this.
==2800== 1. Your program has a bug and erroneously jumped to a non-code
==2800==    location.  If you are running Memcheck and you just saw a
==2800==    warning about a bad jump, it's probably your program's fault.
==2800== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2800==    i.e. it's Valgrind's fault.  If you think this is the case or
==2800==    you are not sure, please let us know and we'll try to fix it.
==2800== Either way, Valgrind will now raise a SIGILL signal which will
==2800== probably kill your program.
==2800==
==2800== Process terminating with default action of signal 4 (SIGILL)
==2800==  Illegal opcode at address 0x5CD8320
==2800==    at 0x5CD8320: ??? (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5CD8F08: ??? (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5CD9998: QRandomGenerator::_fillRange(void*, void*) (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5D37BEB: ??? (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5D38585: QHashData::detach_helper(void (*)(QHashData::Node*, void*), void (*)(QHashData::Node*), int, int) (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5D53C62: ??? (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5D54094: QRegExp::QRegExp(QString const&, Qt::CaseSensitivity, QRegExp::PatternSyntax) (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5DE3C6B: ??? (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5DE477B: QDirIterator::QDirIterator(QString const&, QStringList const&, QFlags<QDir::Filter>, QFlags<QDirIterator::IteratorFlag>) (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5DDDAAB: QDir::entryList(QStringList const&, QFlags<QDir::Filter>, QFlags<QDir::SortFlag>) const (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5DDE11E: QDir::entryList(QFlags<QDir::Filter>, QFlags<QDir::SortFlag>) const (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==    by 0x5EBE259: QFactoryLoader::update() (in /opt/qt510/lib/libQt5Core.so.5.10.1)
==2800==
==2800== HEAP SUMMARY:
==2800==     in use at exit: 97,570 bytes in 67 blocks
==2800==   total heap usage: 241 allocs, 174 frees, 136,991 bytes allocated
==2800==
==2800== LEAK SUMMARY:
==2800==    definitely lost: 0 bytes in 0 blocks
==2800==    indirectly lost: 0 bytes in 0 blocks
==2800==      possibly lost: 0 bytes in 0 blocks
==2800==    still reachable: 97,570 bytes in 67 blocks
==2800==         suppressed: 0 bytes in 0 blocks
==2800== Rerun with --leak-check=full to see details of leaked memory
==2800==
==2800== For counts of detected and suppressed errors, rerun with: -v
==2800== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction