Package: valgrind
Version: 1:3.5.0-3
Severity: normal
Hi,
I'm trying to track down uninitialized memory in some code so I
would like it to have some nice recognisable values. Luckily valgrind
has an option to initialize malloced memory, --malloc-fill. But trying
to use it I always get this error:
% valgrind --malloc-fill=0xcafebabe /bin/sh
valgrind: Bad option '--malloc-fill=0xcafebabe'; aborting.
valgrind: Use --help for more information.
This error is misleading. What it actualy tries to tell me is that
--malloc-fill expects a ONE BYTE hex constant. It should say something
like:
valgrind: Value out of range '--malloc-fill=0xcafebabe'; aborting.
Even better would be if it would accept 1, 2, 4 and 8 byte constants.
The same holds for --free-fill.
MfG
Goswin
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31.6-xen-2010.02.18 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages valgrind depends on:
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libc6-dbg 2.10.2-6 Embedded GNU C Library: detached d
Versions of packages valgrind recommends:
ii gdb 7.0-1 The GNU Debugger
Versions of packages valgrind suggests:
pn alleyoop <none> (no description available)
pn kcachegrind <none> (no description available)
pn valkyrie <none> (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
