#1 deeper stack trace

[Dmitrii Tisnek]

Hi, I would find it much more usable, if dmalloc reported an N-level
deep stack backtrace instead of one return address, for
user-defined value of N.
this kind of functionality would be most useful when debugging code
that uses, for example, STL containers, where an allocation is
triggered after 3 or so levels of function calls.
it should store and report allocation backtrace for unfreed
allocations and free backtrace for erroneous frees, the earlier will,
of course add some overhead, but it's only some tens of bytes :)

If would also be nice if dmalloc could link to libbfd and convert the
addresses to their respective function names, possibly demangled.

P.S. please note this GCC bug if you set to implement this feature
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8743