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

--- Comment #1 from mw <mingwu@gmail.com> ---
Also, currently in the report profilegc.log only the call stack top allocation site is reported, this is not very useful for things like containers from the common library, e.g. array:

void[] std.array.Appender!(char[][]).Appender.ensureAddable.__lambda9

It's much informative to give the full (or top 20 stack traces) to see where the allocation happened in the user code, as what valgrind does.

--

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

--- Comment #2 from mw <mingwu@gmail.com> ---
The nice thing about valgrind is that even if the program segfaults, it can still generate the report file.

profile-gc should have this behavior, instead of insisting on program exit normally.

To debug a out-of-memory problem, you have to terminate the program early, often abnormally.

--

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

RazvanN <razvan.nitu1305@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |razvan.nitu1305@gmail.com
          Component|dmd                         |druntime

--

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

Walter Bright <bugzilla@digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugzilla@digitalmars.com

--- Comment #3 from Walter Bright <bugzilla@digitalmars.com> ---
Calling the function:

    extern (C) int rt_term();

should do the trick.

--