• ciechowoj (7/7) Nov 04 2017 What is the fastest way to have the detailed debug info for
• Joakim (10/18) Nov 05 2017 The symbols for function names are there, just not the DWARF

ciechowoj <keepitsimplesirius gmail.com> writes:

What is the fastest way to have the detailed debug info for 
druntime? I have a program that fails in Fiber constructor after 
I create and delete at least 68_209 Fibers one after another. For 
68_208 works fine, one more and it aborts. I'm trying to use gdb 
to debug, but most likely don't have symbols for druntime. I 
compiled the druntime from source, is there a way to make the 
dmd/dub use the source compiled version?

Joakim <dlang joakim.fea.st> writes:

On Saturday, 4 November 2017 at 21:54:14 UTC, ciechowoj wrote:
 What is the fastest way to have the detailed debug info for 
 druntime? I have a program that fails in Fiber constructor 
 after I create and delete at least 68_209 Fibers one after 
 another. For 68_208 works fine, one more and it aborts. I'm 
 trying to use gdb to debug, but most likely don't have symbols 
 for druntime.

The symbols for function names are there, just not the DWARF 
debug info, if you want to step through the corresponding source 
line by line.

 I compiled the druntime from source, is there a way to make the 
 dmd/dub use the source compiled version?

Assuming you want to use the debug version, you may be better off 
using ldc, which comes with debug versions of druntime and phobos 
and the -link-debuglib option, which will use those instead.  dmd 
and ldc also have the -defaultlib= and -debuglib= options, from 
which you can specify your own or a debug build of the standard 
library, with -debuglib= used if you compile with -g.