• deadalnix (5/5) Aug 16 2015 It looks like every run of whatever I compiled generate a
• Walter Bright (2/6) Aug 16 2015 Bug. Please post to bugzilla as a regression.
• deadalnix (2/12) Aug 17 2015 https://issues.dlang.org/show_bug.cgi?id=14926
• Walter Bright (2/5) Aug 17 2015 thanks!

"deadalnix" <deadalnix gmail.com> writes:

It looks like every run of whatever I compiled generate a 
profilegc.log file, that only contains :

bytes allocated, type, function, file:line

And that's it. Flag used to compile are -w -debug -gc -unittest . 
Bug or feature ?

Walter Bright <newshound2 digitalmars.com> writes:

On 8/16/2015 4:16 PM, deadalnix wrote:
 It looks like every run of whatever I compiled generate a profilegc.log file,
 that only contains :

 bytes allocated, type, function, file:line

 And that's it. Flag used to compile are -w -debug -gc -unittest . Bug or
feature ?

Bug. Please post to bugzilla as a regression.

"deadalnix" <deadalnix gmail.com> writes:

On Sunday, 16 August 2015 at 23:41:28 UTC, Walter Bright wrote:
 On 8/16/2015 4:16 PM, deadalnix wrote:
 It looks like every run of whatever I compiled generate a 
 profilegc.log file,
 that only contains :

 bytes allocated, type, function, file:line

 And that's it. Flag used to compile are -w -debug -gc 
 -unittest . Bug or feature ?

 Bug. Please post to bugzilla as a regression.

https://issues.dlang.org/show_bug.cgi?id=14926

Walter Bright <newshound2 digitalmars.com> writes:

On 8/17/2015 12:50 AM, deadalnix wrote:
 On Sunday, 16 August 2015 at 23:41:28 UTC, Walter Bright wrote:
 Bug. Please post to bugzilla as a regression.

 https://issues.dlang.org/show_bug.cgi?id=14926

thanks!