https://bugs.kde.org/show_bug.cgi?id=445607
--- Comment #2 from Paul Floyd <pjfl...@wanadoo.fr> --- I've done a super quick implementation of clock_getcpuclockid2 [it probably needs a separate i386 version because the 1st param is 64bits]. I now get paulf> ./vg-in-place --soname-synonyms=somalloc=libtcmalloc_minimal.so.4 swipl ==4514== Memcheck, a memory error detector ==4514== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==4514== Using Valgrind-3.19.0.GIT and LibVEX; rerun with -h for copyright info ==4514== Command: swipl ==4514== #Welcome to SWI-Prolog (threaded, 64 bits, version 8.2.3) SWI-Prolog comes with ABSOLUTELY NO WARRANTY. This is free software. Please run ?- license. for legal details. For online help and background, visit https://www.swi-prolog.org For built-in help, use ?- help(Topic). or ?- apropos(Word). ==4514== brk segment overflow in thread #2: can't grow to 0x4820000 ==4514== (see section Limitations in user manual) ==4514== NOTE: further instances of this message will not be shown ==4514== Thread 2 gc: ==4514== Invalid write of size 8 ==4514== at 0x4877C05: tcmalloc::ThreadCache::Init(pthread*) (in /usr/local/lib/libtcmalloc_minimal.so.4.5.9) ==4514== by 0x4878C4D: tcmalloc::ThreadCache::NewHeap(pthread*) (in /usr/local/lib/libtcmalloc_minimal.so.4.5.9) ==4514== by 0x4878A74: tcmalloc::ThreadCache::CreateCacheIfNecessary() (in /usr/local/lib/libtcmalloc_minimal.so.4.5.9) ==4514== by 0x486E115: TCMallocImplementation::MarkThreadBusy() (in /usr/local/lib/libtcmalloc_minimal.so.4.5.9) ==4514== by 0x4AA26F4: ??? (in /usr/local/lib/swipl/lib/amd64-freebsd/libswipl.so.8.2.3) ==4514== by 0x4AB8EC2: PL_next_solution (in /usr/local/lib/swipl/lib/amd64-freebsd/libswipl.so.8.2.3) ==4514== by 0x4AD08DB: PL_call_predicate (in /usr/local/lib/swipl/lib/amd64-freebsd/libswipl.so.8.2.3) ==4514== by 0x4B5C7BC: ??? (in /usr/local/lib/swipl/lib/amd64-freebsd/libswipl.so.8.2.3) ==4514== by 0x529082A: ??? (in /lib/libthr.so.3) ==4514== Address 0x4021000 is not stack'd, malloc'd or (recently) free'd ==4514== ==4514== ==4514== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==4514== Access not within mapped region at address 0x4021000 ==4514== at 0x4877C05: tcmalloc::ThreadCache::Init(pthread*) (in /usr/local/lib/libtcmalloc_minimal.so.4.5.9) ==4514== by 0x4878C4D: tcmalloc::ThreadCache::NewHeap(pthread*) (in /usr/local/lib/libtcmalloc_minimal.so.4.5.9) ==4514== by 0x4878A74: tcmalloc::ThreadCache::CreateCacheIfNecessary() (in /usr/local/lib/libtcmalloc_minimal.so.4.5.9) ==4514== by 0x486E115: TCMallocImplementation::MarkThreadBusy() (in /usr/local/lib/libtcmalloc_minimal.so.4.5.9) ==4514== by 0x4AA26F4: ??? (in /usr/local/lib/swipl/lib/amd64-freebsd/libswipl.so.8.2.3) ==4514== by 0x4AB8EC2: PL_next_solution (in /usr/local/lib/swipl/lib/amd64-freebsd/libswipl.so.8.2.3) ==4514== by 0x4AD08DB: PL_call_predicate (in /usr/local/lib/swipl/lib/amd64-freebsd/libswipl.so.8.2.3) ==4514== by 0x4B5C7BC: ??? (in /usr/local/lib/swipl/lib/amd64-freebsd/libswipl.so.8.2.3) ==4514== by 0x529082A: ??? (in /lib/libthr.so.3) ==4514== If you believe this happened as a result of a stack ==4514== overflow in your program's main thread (unlikely but ==4514== possible), you can try to increase the size of the ==4514== main thread stack using the --main-stacksize= flag. ==4514== The main thread stack size used in this run was 16777216. -- You are receiving this mail because: You are watching all bug changes.
