This is the mail archive of the
mailing list for the GDB project.
Re: D Symbol Demangling
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.
On Mon, 2005-04-04 at 11:21 -0700, Michael Snyder wrote:
> John Demme wrote:
> > Thus far, I've had partial success. In fairly simple D programs, my
> > demangling works, but in more complex programs with mixed C and D code
> > (D is link-compatible with C) it only calls the D demangler for some of
> > the functions.
> What's the granularity of mixed code? Is it mixed within a source
> file, or just between source files? If a source file contains only
> one language, I think gdb ought to be able to discern it reliably.
> When you say "for some of the functions", what differentiates
> the ones where it successfully discerns the D language from those
> where it doesn't?