diff options
| author | Serge Pavlov <sepavloff@gmail.com> | 2016-02-18 16:42:09 +0000 |
|---|---|---|
| committer | Serge Pavlov <sepavloff@gmail.com> | 2016-02-18 16:42:09 +0000 |
| commit | 41c1f79dfe20261a0e427ac50dbead55d4ebd118 (patch) | |
| tree | bbc011ded9141374d75236f98167b5969095ed3b /lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp | |
| parent | eb7e5d90747c73925183af54d5c9fe7b02971afa (diff) | |
| download | bcm5719-llvm-41c1f79dfe20261a0e427ac50dbead55d4ebd118.tar.gz bcm5719-llvm-41c1f79dfe20261a0e427ac50dbead55d4ebd118.zip | |
Avoid double deletion in Clang driver.
Llvm module object is shared between CodeGenerator and BackendConsumer,
in both classes it is stored as std::unique_ptr, which is not a good
design solution and can cause double deletion error. Usually it does
not occur because in BackendConsumer::HandleTranslationUnit the
ownership of CodeGenerator over the module is taken away. If however
this method is not called, the module is deleted twice and compiler crashes.
As the module owned by BackendConsumer is always the same as CodeGenerator
has, pointer to llvm module can be removed from BackendGenerator.
Differential Revision: http://reviews.llvm.org/D15450
llvm-svn: 261222
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp')
0 files changed, 0 insertions, 0 deletions
