Displaying 2 results from an estimated 2 matches for "machonormalizedfilebinarywrit".
Did you mean:
machonormalizedfilebinarywrite
2017 Jul 10
2
Problems generating Mach-O File (x86_64 , osx 10.12)
...n the file StubPass.cpp, specifically in the line 323
<https://github.com/llvm-mirror/lld/blob/master/lib/ReaderWriter/MachO/StubsPass.cpp#L323>
,when
it adds, what it seems an arbitrary number (12) to the offset into the lazy
bind opcodes section, but it should be calculated depending on the
MachONormalizedFileBinaryWrite::lazyBindingInfo result.
I confirmed this bug by patching the code manually in the binary and
writing the right offset in the asm code (__stub_helper). I'm yet not
familiarized with the code , so i can't fix it right now , Im unable to
find the information of the symbols that
MachONormali...
2014 Nov 26
3
[LLVMdev] [lld] memory leaks.
...eturns a pointer without owner.
Maybe a way to fix that issue is to tell that the pointer returned by find() must never be freed, and make sure the FileArchive (and other classes implementing find()) managed the memory of the returned file objects.
- One other leak is Mach-O specific. TrieNode (in MachONormalizedFileBinaryWriter) uses a SmallVector to store its children. But TrieNodes are allocated using a llvm bumpPtr allocator, and so are never ‘deleted'. While the memory used by the TrieNode is properly released when the allocator is destroyed, the SmallVector destructor is never called and so the contained TrieEd...