[Lldb-commits] [lldb] r319653 - Makefile.rules: compile all tests with -fno-limit-debug-info
Pavel Labath via lldb-commits
lldb-commits at lists.llvm.org
Wed Dec 6 04:09:03 PST 2017
On 6 December 2017 at 01:54, Jason Molenda <jmolenda at apple.com> wrote:
> It looks like the macos testsuite on the bot is broken with this -
> On my desktop with a recent clang, it works fine. But it seems like every test? most tests? are failing with
> error: parsing line table prologue at 0x00000000 (parsing ended around 0x00000000
> messages now.
> When I run one test by hand on my system, I have the -fno-limit-debug-info flag:
> ./dotest.py -t -v -v ../packages//Python/lldbsuite/test/functionalities/breakpoint/auto_continue/
> stdout: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -g -O0 -fno-builtin -arch x86_64 -I/Volumes/newwork/svn/lldb/packages/Python/lldbsuite/test/make/../../../../../include -include /Volumes/newwork/svn/lldb/packages/Python/lldbsuite/test/make/test_common.h -I/Volumes/newwork/svn/lldb/packages/Python/lldbsuite/test/make/ -fno-limit-debug-info -std=c99 -c -o main.o main.c
> I'm not sure if the bots are building against too new or too new a compiler - if we're looking at a bug or it just does something weird when given -fno-limit-debug-info?
I was able to reproduce this by running the tests against the
top-of-tree clang (which is what that bot does). It's not all tests
that break, just the ones using dSYM debug info.
While this patch is a reasonable first guess, it is actually *not* the
source of the breakage. The culprit is
<https://reviews.llvm.org/D38002>, which was present in the same
patchset. It seems this change makes clang emit different line table
headers. After that, dsymutil fails to process the files because it
detects a header mismatch (and lldb breaks because it cannot find the
line table or it is corrupt). I've cc'ed Paul in case he has any
Maybe dsymutil needs to be updated to handle the new line tables?
More information about the lldb-commits