[phobos] Stack traces in druntime/phobos

Sean Kelly sean at invisibleduck.org
Tue Sep 21 16:29:17 PDT 2010


Pretty slick.  I was hoping to avoid reading the map file if possible though, and use StackWalk64 for the trace.

On Sep 18, 2010, at 6:56 PM, Denis wrote:

> I've made an attempt to intergrate stack tracer into druntime,
> modified runtime.d is attached to this message.
> 
> It also relies on codeview.d (which I placed into core.sys.windows
> package because it is Windows specific). Strictly speaking, it isn't
> mandatory for stack traces to work and I I can get rid of it if you
> believe it doesn't belong to druntime, but it adds module names and
> line numbers to stack trace (which I believe is a good thing to have).
> 
> Symbol names are extracted from a dmd-generated map file. Compile with
> -g -map for the best trace info.
> 
> It does quite a few of memory allocations, so generating call-stack
> for an OutOfMemory exception may result in a stack overflow. It's an
> issue I can fix, but it's far from being a trivial one.
> <changes.zip>_______________________________________________
> phobos mailing list
> phobos at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos



More information about the phobos mailing list