DMD's codeview types for arrays

[Lars Ivar Igesund]

Walter Bright wrote:

> Jascha Wetzel wrote:
>> Walter Bright wrote:
>>> Sure, but I suggest a better way - add our own extension to CV data.
>> 
>> ok, i can think of type leafs similar to this (notation according to CV
>> specs):
>> size content
>> 2    LF_DYN_ARRAY (define as 0x0017)
>> 2    @elemtype
>> 
>> and
>> 2    LF_ASSOC_ARRAY (define as 0x0018)
>> 2    @elemtype
>> 2    @keytype
>> 
>> couldn't that also trigger the problem with functions returning such
>> types?
> 
> 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,

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.

For reference,
http://d.puremagic.com/issues/show_bug.cgi?id=136

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