diff options
| author | Bjorn Steinbrink <bsteinbr@gmail.com> | 2014-09-05 21:22:09 +0000 |
|---|---|---|
| committer | Bjorn Steinbrink <bsteinbr@gmail.com> | 2014-09-05 21:22:09 +0000 |
| commit | 5a121b2ef58e16d9565515126fc560bbe5d24eb5 (patch) | |
| tree | ef9e540ef7d0a3c6ae8b7ddc0161f193b7ce3b06 /lldb/scripts/Python/python-wrapper.swig | |
| parent | f4b8debc1c6c030f241a0acc2d38d7e100cde65a (diff) | |
| download | llvm-5a121b2ef58e16d9565515126fc560bbe5d24eb5.zip llvm-5a121b2ef58e16d9565515126fc560bbe5d24eb5.tar.gz llvm-5a121b2ef58e16d9565515126fc560bbe5d24eb5.tar.bz2 | |
Restore the ability to check if LLVMCreateObjectFile was successful
Summary:
Until r216870 LLVMCreateObjectFile returned nullptr in case of an error,
so callers could check if the call was successful. Now, it always
returns an OwningBinary wrapped as an LLVMObjectFileRef, so callers
can't check if the call was successul.
This results in a segfault running e.g.
llvm-c-test --object-list-sections < /dev/null
So the old behaviour should be restored.
Subscribers: llvm-commits
Differential Revision: http://reviews.llvm.org/D5143
llvm-svn: 217279
Diffstat (limited to 'lldb/scripts/Python/python-wrapper.swig')
0 files changed, 0 insertions, 0 deletions