Package: valgrind Version: 1:3.2.3-3 Severity: normal
Programs that free memory via realloc (e.g. "realloc (ptr, 0)") create spurious leak messages: ==19046== 0 bytes in 1 blocks are definitely lost in loss record 14 of 15 ==19046== at 0x4C21C16: malloc (vg_replace_malloc.c:149) ==19046== by 0x4C21C90: realloc (vg_replace_malloc.c:306) 0 bytes doesn't look like a big leak (but likely it creates a real leak inside valgrind if it doesn't properly free the block). Additional Information: POSIX/SUS and the windows runtime library both mandate that realloc (ptr, 0) acts like free (ptr), and on other systems this is usually implemented as an extension to whatever older standard they might or might not follow (however, ISO C doesn't mandate it, but valgrind shouldn't enforce ISO C limitations on POSIX functions). -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.21-2-amd64 Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages valgrind depends on: hi libc6 2.6.1-1 GNU C Library: Shared libraries Versions of packages valgrind recommends: hi gdb 6.6.dfsg-1 The GNU Debugger -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
