Unable to use tradional tools to find memory leaks

[David Nadlinger]

On Saturday, 21 September 2013 at 17:03:14 UTC, Brad Roberts 
wrote:
> That's wrong.  Both DMD and Valgrind are software, both of 
> which can be debugged and changed. Please file appropriate bug 
> reports, hopefully with nicely minimized test cases.

I ran into an issue like this once where DMD would generate a 
strange instruction prefix on Linux x86_64 that was not supported 
by Valgrind. Never went on to check whether it was actually legal 
though.

If I recall correctly, Valgrind reports details about the 
problematic instruction on the console before it terminates. If 
its an instruction encoding issue, just disassemble your program 
at/around the given address (e.g. using objdump -d) and post the 
result together with the error message.

David