> Speculation beyond the original question: > Given that it's a pretty common/core feature of a debugger to call functions, > perhaps a start would be some way for the producer to communicate, via DWARF, > that it has changed the ABI of a function and so the consumer should not try > to synthesize calls to it. Providing much more functionality than that I > think will amount to encoding the ad-hoc ABIs that compilers create in these > situations (possible, but a fairly non-trivial proposal/enhancement to DWARF)
I believe that's what DW_AT_calling_convention and DW_CC_nocall are for (Section 3.3.1.1). -cary _______________________________________________ Dwarf-Discuss mailing list Dwarf-Discuss@lists.dwarfstd.org http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
