DWARF output, type of char[]?

[Cristian Vlasceanu]

BCS Wrote:

> Frits van Bommel wrote:
> > Cristian Vlasceanu wrote:
> > 
> >> I do not know enough D, but is there "unsigned long long" an otherwise 
> >> legal D type? Because if (as I supsect) it isn't, and it can be 
> >> unequivocally determined that it stands for  a char[] whenever the 
> >> translation unit's language is D, I could easily make it work in Zero. 
> >> Out of the box.
> > 
> > 
> > You may want to check what type "ulong" is marked as. Since that's a 
> > 64-bit unsigned integer (like unsigned long long typically is) it may 
> > also be marked as "unsigned long long"...
> 
> What is needed is for T[] to be marked as something special. Then you 
> could treat it as described. FWIW D has it's own DWARF "language number" 
> so we should be able to add new types. Then the debugger could treat it 
> as said struct.
> 
> A short term hack could be to have the compiler do the magic and mark it 
> as some sort of auto generated struct type.
> 
> Disclaimer: I know slightly more than 0 about how DWARF works under the 
> hood.


I have verified this, with 1.010, ulong and char[] are indistinguishable in the DWARF.

My personal preference is to have it represented as a struct.