[LLVMdev] Extra padding on DWARF debug info?

Nick Kledzik kledzik at apple.com
Wed Apr 13 12:02:09 PDT 2011

On Apr 13, 2011, at 11:15 AM, Chris Lattner wrote:
>>> Does anybody know what the bug is in GDB that this works around? The
>>> workaround was added as part of r103439[1], which added support for
>>> multiple compilation units in one module. Does the bug ever affect
>>> modules with only a single compilation unit?
>> It was not added by r103439. In fact, it was added by r32035.
>> http://llvm.org/viewvc/llvm-project?view=rev&revision=32035 
>> Unfortunately the log message and comments do not provide any hints, and I do not have access to the author anymore.
> Sounds like we should rip it out and see if there is any regression on the gdb testsuite.
I vaguely recall an issue (maybe a linker related) when the DWARF debug_line table was empty (source file with no functions).  The fix was to pad out the line table with a couple of no-ops.  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110413/5e540415/attachment.html>

More information about the llvm-dev mailing list