Will Song via llvm-dev
2017-Jul-06 17:55 UTC
[llvm-dev] ErrorInfo::message() possibly broken in LLVM-4.0.1
Hello,
I have the following snippet of code that causes valgrind to freak out
over unitialized bytes.
llvm::Expected<llvm::object::OwningBinary<llvm::object::ObjectFile>>
e
= llvm::object::ObjectFile::createObjectFile(llvm::StringRef(fname));
if (!e) {
llvm::handleAllErrors(e.takeError(),
[](const llvm::ErrorInfo<llvm::ECError> &EI)
{
std::cerr << EI.message() << std::endl;
});
return 1;
}
Am I doing something wrong here?
--
Will Song
Will Song via llvm-dev
2017-Jul-06 18:53 UTC
[llvm-dev] ErrorInfo::message() possibly broken in LLVM-4.0.1
Looks like a problem on my end. I should have compiled LLVM against libc++. -- Will Song
Tom Stellard via llvm-dev
2017-Jul-06 18:55 UTC
[llvm-dev] ErrorInfo::message() possibly broken in LLVM-4.0.1
On 07/06/2017 02:53 PM, Will Song via llvm-dev wrote:> Looks like a problem on my end. I should have compiled LLVM against > libc++. >libstdc++ should work too, can you file a bug for this? -Tom
Seemingly Similar Threads
- Interest in integrating a linux perf JITEventListener?
- [LLVMdev] SymbolRef and getSize
- [LLVMdev] How to get the symbols from a .so file?
- [LLVMdev] llvm-ar does not generates symbol table for contained bitcode files
- [LLVMdev] llvm-ar does not generates symbol table for contained bitcode files