https://bugs.kde.org/show_bug.cgi?id=520170

Paul Floyd <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |RESOLVED
         Resolution|---                         |NOT A BUG

--- Comment #11 from Paul Floyd <[email protected]> ---
>From what I see, you are using TCMalloc:

sym at 0x50209b0: prefer 'nallocx' to 'tc_nallocx'
sym at 0x50214c0: prefer 'tc_malloc' to '__libc_malloc'
sym at 0x50214c0: prefer 'malloc' to 'tc_malloc'
sym at 0x5021580: prefer 'cfree' to 'tc_cfree'
sym at 0x5021580: prefer 'cfree' to '__libc_cfree'
sym at 0x5021580: prefer 'cfree' to '__libc_free'
sym at 0x5021580: prefer 'cfree' to 'tc_free'
sym at 0x5021580: prefer 'cfree' to '_ZdlPv'
sym at 0x5021580: prefer 'cfree' to '_ZdaPv'
sym at 0x5021580: prefer 'cfree' to 'tc_delete'
sym at 0x5021580: prefer 'cfree' to 'tc_deletearray'
sym at 0x5021580: prefer 'free' to 'cfree'
sym at 0x50216d0: prefer '_ZN13TCMallocGuardC1Ev' to '_ZN13TCMallocGuardC2Ev'
sym at 0x5021740: prefer '_ZdlPvm' to 'tc_free_sized'
sym at 0x5021740: prefer '_ZdlPvm' to 'tc_delete_sized'
sym at 0x5021740: prefer '_ZdaPvm' to '_ZdlPvm'
sym at 0x5021740: prefer '_ZdaPvm' to 'free_sized'
sym at 0x5021740: prefer '_ZdaPvm' to 'tc_deletearray_sized'
sym at 0x50218b0: prefer 'calloc' to '__libc_calloc'
sym at 0x50218b0: prefer 'calloc' to 'tc_calloc'
sym at 0x5021aa0: prefer 'tc_realloc' to '__libc_realloc'
sym at 0x5021aa0: prefer 'realloc' to 'tc_realloc'
sym at 0x5022280: prefer '_Znwm' to 'tc_new'
sym at 0x5022280: prefer '_Znwm' to 'tc_newarray'

(all those tc_ prefix functions are from TCMalloc).

That means you have 3 choices, as described in the FAQ

1. Build with a version of TCMalloc that does not optimize deallocation
functions by using aliases (a debug byuld of TCMalloc or build it with
CPPFLAGS=-DTCMALLOC_NO_ALIASES
2. Do not link with tcmalloc
3. Use --show-mismatched-frees=no. You will then miss any genuine mismatches in
your code. It's not the most dangerous error, so that isn't too bad an option.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to