diff options
| author | Peter Collingbourne <peter@pcc.me.uk> | 2016-05-05 04:10:12 +0000 |
|---|---|---|
| committer | Peter Collingbourne <peter@pcc.me.uk> | 2016-05-05 04:10:12 +0000 |
| commit | e29e142a102d3f3126f6a7627134b10af3a93b2f (patch) | |
| tree | 96357e103a732c9f080f7986c86cdc5414d97084 /lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp | |
| parent | 2cb6f0ce29afdf489189876aa68b2220fb258db9 (diff) | |
| download | bcm5719-llvm-e29e142a102d3f3126f6a7627134b10af3a93b2f.tar.gz bcm5719-llvm-e29e142a102d3f3126f6a7627134b10af3a93b2f.zip | |
ELF: Do not use -1 to mark pieces of merge sections as being tail merged.
We were previously using an output offset of -1 for both GC'd and tail
merged pieces. We need to distinguish these two cases in order to filter
GC'd symbols from the symbol table -- we were previously asserting when we
asked for the VA of a symbol pointing into a dead piece, which would end
up asking the tail merging string table for an offset even though we hadn't
initialized it properly.
This patch fixes the bug by using an offset of -1 to exclusively mean GC'd
pieces, using 0 for tail merges, and distinguishing the tail merge case from
an offset of 0 by asking the output section whether it is tail merge.
Differential Revision: http://reviews.llvm.org/D19953
llvm-svn: 268604
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp')
0 files changed, 0 insertions, 0 deletions
