Walter Bright wrote:
> No, because you can fix your debugger. What I'd do is the same thing I do with gdb, -g generates D debug info and needs a debugger aware of it, -gc generates C debug info for debuggers that aren't. In this case, the C debug info will not change.

ok, great!
so, are the custom type leafs the kind of extension you have in mind?
i'd prepare my code for that, then.

Lars Ivar Igesund wrote:
> Walter Bright wrote:
> Except that the stack backtrace is broken using -g (although it is possible
> to find _some_ linenumbers). Dropping -g works much better, although no
> line numbers are present.

this problem is probably elf/dwarf related. the codeview stuff is win32 only.

[firstname] wrote:

> Lars Ivar Igesund wrote:
>> Walter Bright wrote:
>> Except that the stack backtrace is broken using -g (although it is
>> possible to find _some_ linenumbers). Dropping -g works much better,
>> although no line numbers are present.
> 
> this problem is probably elf/dwarf related. the codeview stuff is win32 only.

True, this is a DMD for Linux problem. I thought it was suggested earlier in the thread, but possibly not :)

-- 
Lars Ivar Igesund
blog at http://larsivi.net
DSource & #D: larsivi
Dancing the Tango