quasselcore@michaelmarley:/home/michael$ valgrind --leak-check=yes /usr/bin/quasselcore --configdir=/var/lib/quassel --syslog --logle
vel=Info --port=4242 --ident-daemon --strict-ident --require-ssl | tee /var/lib/quassel/valgrind.txt
==20343== Memcheck, a memory error detector
==20343== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==20343== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==20343== Command: /usr/bin/quasselcore --configdir=/var/lib/quassel --syslog --loglevel=Info --port=4242 --ident-daemon --strict-ide
nt --require-ssl
==20343==
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
==20343== Warning: set address range perms: large range [0x59c47000, 0xd9c47000) (defined)
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
==20343== Thread 5 QThread:
==20343== Conditional jump or move depends on uninitialised value(s)
==20343==    at 0x2BEB82: Network::setNetworkInfo(NetworkInfo const&) (network.cpp:151)
==20343==    by 0x20052D: CoreSession::createNetwork(NetworkInfo const&, QStringList const&) (coresession.cpp:630)
==20343==    by 0x2020F7: CoreSession::loadSettings() (coresession.cpp:232)
==20343==    by 0x203E2C: CoreSession::CoreSession(UserId, bool, bool, QObject*) (coresession.cpp:121)
==20343==    by 0x2534E6: initialize (sessionthread.cpp:48)
==20343==    by 0x2534E6: (anonymous namespace)::Worker::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (sessionthread.
moc:87)
==20343==    by 0x556C44A: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3787)
==20343==    by 0x538A506: QThread::started(QThread::QPrivateSignal) (moc_qthread.cpp:162)
==20343==    by 0x538C8CA: QThreadPrivate::start(void*) (qthread_unix.cpp:356)
==20343==    by 0x5BEF163: start_thread (pthread_create.c:486)
==20343==    by 0x5B15DEE: clone (clone.S:95)
==20343==
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
==20343== Conditional jump or move depends on uninitialised value(s)
==20343==    at 0x1F5238: CoreNetwork::updateRateLimiting(bool) (corenetwork.cpp:1029)
==20343==    by 0x1FCA8A: CoreNetwork::socketInitialized() (corenetwork.cpp:595)
==20343==    by 0x1B069E: CoreNetwork::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (moc_corenetwork.cpp:505)
==20343==    by 0x556C44A: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3787)
==20343==    by 0x496A68A: QSslSocketPrivate::_q_connectedSlot() (qsslsocket.cpp:2483)
==20343==    by 0x4970A48: QSslSocket::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (moc_qsslsocket.cpp:175)
==20343==    by 0x556C44A: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3787)
==20343==    by 0x49350D2: QAbstractSocketPrivate::fetchConnectionParameters() (qabstractsocket.cpp:1367)
==20343==    by 0x4937F4F: QAbstractSocketPrivate::_q_testConnection() (qabstractsocket.cpp:1180)
==20343==    by 0x494704C: QWriteNotifier::event(QEvent*) (qnativesocketengine.cpp:1307)
==20343==    by 0x5542705: doNotify (qcoreapplication.cpp:1147)
==20343==    by 0x5542705: notify (qcoreapplication.cpp:1133)
==20343==    by 0x5542705: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1057)
==20343==    by 0x5597804: socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) (qeventdispatcher_glib.cpp:106)
==20343==
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.
--20343-- WARNING: unhandled amd64-linux syscall: 332
--20343-- You may be able to write your own handler.
--20343-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--20343-- Nevertheless we consider this a bug.  Please report
--20343-- it at http://valgrind.org/support/bug_reports.html.