thread_attachThis creates an instance of Thread class for the
main process thread during runtime initialization:
https://github.com/D-Programming-Language/druntime/blob/master/src/core/thread.d#L1792
oops, no, there's no malloc there.
But still it must be allocated somehow, probably GC is
substituted for C heap.
On Monday, 27 January 2014 at 09:44:50 UTC, Thejaswi Puthraya
wrote:
==11356== 16 bytes in 1 blocks are definitely lost in loss
record 1 of 2
==11356==at 0x4A0645D: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==11356==by 0x43E366: thread_attachThis (in /home/theju/
On Friday, 31 January 2014 at 21:00:38 UTC, Rob wrote:
This same question appears to have been answered here, but it's
not really conclusive
http://stackoverflow.com/questions/14802212/memory-leak-in-minimal-d-program
On 2014-01-27 01:44, Thejaswi Puthraya wrote:
I have a simple "Hello World"
This same question appears to have been answered here, but it's not
really conclusive
http://stackoverflow.com/questions/14802212/memory-leak-in-minimal-d-program
On 2014-01-27 01:44, Thejaswi Puthraya wrote:
I have a simple "Hello World" program (file named "tmp.d") written in D
import std.s
I have a simple "Hello World" program (file named "tmp.d")
written in D
import std.stdio;
void main() {
printf("Hello World\n");
}
I successfully compiled the above program with the DMD64 D
compiler v2.064 on linux x86_64 (libc 2.18 just in case
required). But valgrind reports memory leaks
