search for: running_tid

...ing: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x2a valgrind: m_debuginfo/readdwarf.c:2292 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed. ==29007== at 0x3802B1F7: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) sched status: running_tid=0 Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, espec...

...==18130== by 0x3801E69C: vgPlain_assert_fail (m_libcassert.c:267) ==18130== by 0x3800FCD9: vgCallgrind_get_jcc (jumps.c:164) ==18130== by 0x38003534: vgCallgrind_push_call_stack (callstack.c:217) ==18130== by 0x38001FDB: vgCallgrind_setup_bbcc (bbcc.c:844) ==18130== by 0x6292A7E3: ??? sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==18130== at 0x3E30CB0: std::ios_base::Init::Init() (in /usr/lib/libstdc++.so.6.0.8) ==18130== by 0x3EA0125: ??? (in /usr/lib/libstdc++.so.6.0.8) ==18130== by 0x3E22BD0: ??? (in /usr/lib/libstdc++.so.6.0.8) ==18130== by 0xAE2162: call_init (in /lib/ld-2.5.so) ==18...

...d/memcheck-amd64-linux) > ==20179== by 0x380D296B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) > ==20179== by 0x380D45CF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) > ==20179== by 0x380E3946: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) > > sched status: > running_tid=1 > > Thread 1: status = VgTs_Runnable (lwpid 20179) > ==20179== at 0x5DE7E00: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) > ==20179== by 0x5DC70BF: EC_POINT_mul (in > /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) > ==20179== by 0x5DC5F06: EC_POINT_new (in > /lib/...

...1C0B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==20179== by 0x380D296B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==20179== by 0x380D45CF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==20179== by 0x380E3946: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 20179) ==20179== at 0x5DE7E00: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==20179== by 0x5DC70BF: EC_POINT_mul (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==20179== by 0x5DC5F06: EC_POINT_new (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0...

...>> ==20179== by 0x380D296B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) >> ==20179== by 0x380D45CF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) >> ==20179== by 0x380E3946: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) >> >> sched status: >> running_tid=1 >> >> Thread 1: status = VgTs_Runnable (lwpid 20179) >> ==20179== at 0x5DE7E00: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) >> ==20179== by 0x5DC70BF: EC_POINT_mul (in >> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) >> ==20179== by 0x5DC5F06: EC_POI...

http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good and stable v2.2.26 out. * master: Removed hardcoded 511 backlog limit for listen(). The kernel should limit this as needed. * doveadm import: Source user is now initialized

http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good and stable v2.2.26 out. * master: Removed hardcoded 511 backlog limit for listen(). The kernel should limit this as needed. * doveadm import: Source user is now initialized