This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: D Symbol Demangling

John Demme wrote:
By link compatible, I mean that I'll compile a D file with a D compiler
to a .o file, then I can link it with another .o file compiled with,
say, gcc.  So a source file can be either C or D, but not both (barring
some sort of bizarre scripting situations.)  An important note here,
however, is that because D can call C functions, some of the symbols in
a D object file won't be mangled.

I've been having trouble figuring out what differentiates the functions.
On the surface, the more complex ones don't work, but in my test,
there's only simple one.

Do I appear to be interfacing with GDB correctly?  If so, I'll triple
check my code.

Looks ok at first glance. Do I understand that the D compiler is not gcc or gcc-derived? That raises the question of whether the debug info in the D-compiled .o file is "correct" as far as gdb is concerned. Something unexpected about that info might cause gdb to "lose its place", eg. in determining which functions belong to the D-compiled module.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]