The new API allows to find a list of compile units related to target/module.
Details
Diff Detail
Event Timeline
This seems like a reasonable addition. Could you also add documentation for the new API?
include/lldb/API/SBModule.h | ||
---|---|---|
136 | We typically use \param instead of @param in LLVM. | |
packages/Python/lldbsuite/test/python_api/module_section/TestModuleAndSection.py | ||
151 | shouldn't this be self.getBuildArtifact('b.out')? | |
packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py | ||
54 | shouldn't this be self.getBuildArtifact('b.out')? |
packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py | ||
---|---|---|
54 | Do you mean: shouldn't self.getBuildArtifact be as a find_compile_units parameter? |
include/lldb/API/SBModule.h | ||
---|---|---|
136 | I did it like it's done in other places in lldb. Are you sure about \param and @param? |
Fre
packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py | ||
---|---|---|
54 | self.find_compile_units(self.getBuildArtifact('b.out')) |
We typically use \param instead of @param in LLVM.