[cfe-commits] r167799 - /cfe/trunk/lib/Driver/Tools.cpp

[Eric Christopher]

> dtrace uses the accelerator tables? How and why? The accelerator tables
> are built from the debug info that's going into the final file, I think
> you're conflating two problems here.
> >
> dtrace is munging through a bunch of code, some of it is the debug info.
> The accelerator tables are fubared going into the dtrace mode. Once I
> turned off the accel tables, the 'dwarfdump --verify' reported no errors.
> However, dtrace is still thrashing. I have to investigate via dtrace
> debugging and junk. But I still think this patch is worth keeping in for
> the time being, because it makes dwarfdump happy, which is certain to be an
> error during an Apple-style build...


What I'm saying is that I don't think you've identified the problem. If the
accelerator tables are munged it's because the rest of the debug
information is munged. Can you show a testcase, or problem, or anything
here?

Do you have a particular set of output from the verify to show what's going
on here?

-eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20121113/06039e67/attachment.html>