https://bugs.kde.org/show_bug.cgi?id=378732
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m...@klomp.org
--- Comment #8 from Mark Wielaard <m...@klomp.org> ---
I think the problem is that bash not only has its own malloc/free
implementation (valgrind should intercept that just fine). But also has malloc
wrappers for some malloc functions that call their internal counterparts
directly (so valgrind won't know that is a matching allocation/deallocation
function).
See xmalloc.h:
#if defined(USING_BASH_MALLOC) && !defined (DISABLE_MALLOC_WRAPPERS)
extern PTR_T sh_xmalloc __P((size_t, const char *, int));
extern PTR_T sh_xrealloc __P((void *, size_t, const char *, int));
extern void sh_xfree __P((void *, const char *, int));
#define xmalloc(x) sh_xmalloc((x), __FILE__, __LINE__)
#define xrealloc(x, n) sh_xrealloc((x), (n), __FILE__, __LINE__)
#define xfree(x) sh_xfree((x), __FILE__, __LINE__)
#ifdef free
#undef free
#endif
#define free(x) sh_xfree((x), __FILE__, __LINE__)
#endif /* USING_BASH_MALLOC */
--
You are receiving this mail because:
You are watching all bug changes.
