maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/tools/dsymutil/absolute_symbol.test

18 lines
501 B
Plaintext
Raw Normal View History

[dsymutil] Ignore absolute symbols in the debug map Quoting from the comment added to the code: // Objective-C on i386 uses artificial absolute symbols to // perform some link time checks. Those symbols have a fixed 0 // address that might conflict with real symbols in the object // file. As I cannot see a way for absolute symbols to find // their way into the debug information, let's just ignore those. llvm-svn: 255350
2015-12-12 01:50:37 +08:00
RUN: llvm-dsymutil -dump-debug-map -oso-prepend-path %p %p/Inputs/absolute_sym.macho.i386 | FileCheck %s
The tested object file has been created by the dummy Objective-C code:
@interface Foo
@end
@implementation Foo
@end
int main() { return 0; }
compiled for i386. This create an absolute symbol .objc_class_name_Foo
We must not consider this symbol for debug info linking as its address
might conflict with other real symbols in the same file.
[dsymutil] Fix handling of common symbols. llvm-dsymutil was misinterpreting the value of common symbols as their address when it actually contains their size. This didn't impact llvm-dsymutil's ability to link the debug information for common symbols because these are always found by name and not by address. Things could however go wrong when the size of a common object matched the object file address of another symbol. Depending on the link order of the symbols the common object might incorrectly evict this other object from the address to symbol mapping, and then link the evicted symbol with a wrong binary address. Use the new ability to have symbols without an object file address to fix this. llvm-svn: 259318
2016-01-31 12:29:34 +08:00
CHECK: objc_class_name_Foo
CHECK-SAME-NOT: objAddr