https://bugs.kde.org/show_bug.cgi?id=357833
Tom Hughes <t...@compton.nu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |t...@compton.nu --- Comment #1 from Tom Hughes <t...@compton.nu> --- I presume that this code in coregrind/m_main.c is the issue (so will affect all tools, not just memcheck): //-------------------------------------------------------------- // Get the current process datasize rlimit, and set it to zero. // This prevents any internal uses of brk() from having any effect. // We remember the old value so we can restore it on exec, so that // child processes will have a reasonable brk value. VG_(getrlimit)(VKI_RLIMIT_DATA, &VG_(client_rlimit_data)); zero.rlim_max = VG_(client_rlimit_data).rlim_max; VG_(setrlimit)(VKI_RLIMIT_DATA, &zero); The logic is self-explanatory, but equally it seems it is only an attempt to detect mistakes in valgrind, so that any attempt to allocate memory with brk() would fail. -- You are receiving this mail because: You are watching all bug changes.