Displaying 3 results from an estimated 3 matches for "dbgfunctype".
2010 Sep 05
0
[LLVMdev] More DIFactory questions - still stumped
On 5 September 2010 19:32, Talin <viridia at gmail.com> wrote:
> I've carefully studied the source code of CGDebugInfo in clang as a working
> example. One puzzlement is that there's a discrepancy between what the
> "source level debugging with LLVM" docs say and what clang does: According
> to the docs, DW_TAG_formal_parameter is used to specify a formal
2010 Sep 06
2
[LLVMdev] More DIFactory questions - still stumped
...me parts are commented out for debugging purposes):
DISubprogram CodeGenerator::genDISubprogram(const FunctionDefn * fn,
Function * f) {
DASSERT(fn != NULL);
// Look up in the map to see if already generated.
DISubprogram & sp = dbgSubprograms_[fn];
if (!sp.isSubprogram()) {
DIType dbgFuncType = genDIType(fn->functionType());
DASSERT(dbgFuncType.Verify());
DASSERT(dbgCompileUnit_.Verify());
sp = dbgFactory_.CreateSubprogram(
dbgCompileUnit_,
fn->name(),
fn->qualifiedName(),
fn->linkageName(),
dbgFile_, // genDIFile(fn),...
2010 Sep 05
2
[LLVMdev] More DIFactory questions - still stumped
I hate to be a nag, but after several days of working on this I am still
utterly stumped.
Let me recap the situation as it currently stands: I'm trying to write code
that generates DWARF debugging information for my compiler using DIFactory
and friends. Unfortunately the information I am generating appears to be
invalid, but I can't figure out the cause.
Based on the advice in the