https://bugs.kde.org/show_bug.cgi?id=512127
--- Comment #2 from Paul Floyd <[email protected]> --- The main part of the problem is ==77391== Process terminating with default action of signal 11 (SIGSEGV) ==77391== Access not within mapped region at address 0x70000639A41A ==77391== at 0x1006754A3: _pthread_join_cleanup (in /usr/lib/system/libsystem_pthread.dylib) ==77391== by 0x10067786F: _pthread_join (in /usr/lib/system/libsystem_pthread.dylib) ==77391== by 0x100000BE5: main (thread_alloca.c:50) ==77391== If you believe this happened as a result of a stack ==77391== overflow in your program's main thread (unlikely but ==77391== possible), you can try to increase the size of the ==77391== main thread stack using the --main-stacksize= flag. ==77391== The main thread stack size used in this run was 8388608. The second issue Memcheck: mc_leakcheck.c:1128 (void lc_scan_memory(Addr, SizeT, Bool, Int, Int, Addr, SizeT)): Assertion 'bad_scanned_addr >= VG_ROUNDUP(start, sizeof(Addr))' failed. host stacktrace: ==77391== at 0x258059CD9: ??? (m_libcassert.c:426) ==77391== by 0x25805A04F: ??? (m_libcassert.c:497) ==77391== by 0x25805A024: ??? (m_libcassert.c:564) ==77391== by 0x258003C05: ??? (mc_leakcheck.c:1128) ==77391== by 0x258003424: ??? (mc_leakcheck.c:2028) ==77391== by 0x258001CB2: ??? (mc_leakcheck.c:2235) ==77391== by 0x258017660: ??? (mc_main.c:8493) ==77391== by 0x25815BE13: ??? (m_main.c:2316) ==77391== by 0x258127774: ??? (syswrap-darwin.c:246) My guesss is that fixing the first segfault will make the leak alignment assert go away. -- You are receiving this mail because: You are watching all bug changes.
