I tried the testcase provided on kde's bug repport, and it is still working on my machine: w...@celine:~/debian-fix/valgrind-test% valgrind ./mremap_test ==2811== Memcheck, a memory error detector ==2811== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==2811== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright info ==2811== Command: ./mremap_test ==2811== 0x4020000 - 0x4021000 4096 0x4022000 - 0x4024000 8192 0x4024000 - 0x4028000 16384 0x4028000 - 0x4030000 32768 0x4030000 - 0x4040000 65536 0x4046000 - 0x4066000 131072 0x4066000 - 0x40a6000 262144 0x40a6000 - 0x4126000 524288 0x517a000 - 0x527a000 1048576 0x527a000 - 0x547a000 2097152 ==2811== ==2811== HEAP SUMMARY: ==2811== in use at exit: 0 bytes in 0 blocks ==2811== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==2811== ==2811== All heap blocks were freed -- no leaks are possible ==2811== ==2811== For counts of detected and suppressed errors, rerun with: -v ==2811== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)
Maybe it depends on the linux kernel version, or the architecture. On Mon, Feb 15, 2010 at 9:50 AM, Pierre Habouzit <[email protected]>wrote: > I fail to reproduce it with minimal testcases. Though it is known > upstream: > > https://bugs.kde.org/show_bug.cgi?id=204484 > > I have very similar backtraces here. > >
