Report a bug
If you spot a problem with this page, click here to create a Bugzilla issue.
Improve this page
Quickly fork, edit online, and submit a pull request for this page.
Requires a signed-in GitHub account. This works well for small changes.
If you'd like to make larger changes you may want to consider using
a local clone.
etc.valgrind.valgrind
D wrapper for the Valgrind client API.
Note that you must include this file into your program's compilation
and compile with -debug=VALGRIND to access the declarations below.
- nothrow @nogc void
makeMemNoAccess(const(void)[]mem); - Mark the memory covered by
memas unaddressable. - nothrow @nogc void
makeMemUndefined(const(void)[]mem); - Similarly, mark memory covered by
memas addressable but undefined. - nothrow @nogc void
makeMemDefined(const(void)[]mem); - Similarly, mark memory covered by
memas addressable and defined. - nothrow @nogc uint
getVBits(const(void)[]mem, ubyte[]bits); - Get the validity data for the address range covered by
memand copy it into the providedbitsarray.Returns:- 0 if not running on valgrind
- 1 success
- 2 [previously indicated unaligned arrays; these are now allowed]
- 3 if any parts of
mem/bitsare not addressable.
- nothrow @nogc uint
setVBits(const(void)[]mem, ubyte[]bits); - Set the validity data for the address range covered by
mem, copying it from the providedbitsarray.Returns:- 0 if not running on valgrind
- 1 success
- 2 [previously indicated unaligned arrays; these are now allowed]
- 3 if any parts of
mem/bitsare not addressable.
- nothrow @nogc void
disableAddrReportingInRange(const(void)[]mem);
nothrow @nogc voidenableAddrReportingInRange(const(void)[]mem); - Disable and re-enable reporting of addressing errors in the address range covered by
mem.
Copyright © 1999-2026 by the D Language Foundation | Page generated by
Ddoc on Wed Aug 5 15:49:02 2026