SBSection::GetSectionData and Section::GetSectionData are
implemented differently, and the SBSection method doesn't handle
compressed sections correctly.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
lldb/source/API/SBSection.cpp | ||
---|---|---|
187–189 | Probably either use std::move when passing result_data_sp to SetOpaque, or roll the expressions together (to avoid an unnecessary copy of a ref counted smart pointer, that would cause extra increment/decrement of the ref count) |
lldb/source/API/SBSection.cpp | ||
---|---|---|
187–189 | Done, inlined result_data_sp into the SetOpaque call. Thanks! |
LLDB windows buildbots were broken by the TestSectionAPI.py test. I dont
have full context of the commit to fix it. Reverting it temporarily.
https://lab.llvm.org/buildbot/#/builders/83/builds/28617
https://lab.llvm.org/buildbot/#/builders/219/builds/180
I'm pretty sure that's because that bot builds without zlib support. You'll need to add something like @skipIfXmlSupportMissing to this test (I think we don't have a decorator for zlib now, so you'll probably need to add one).
While you're at it, you might as well slap @no_debug_info_test on it.
I'm sorry Omair, my comment was meant for Jorge, not you. @skipIfXml is not the right decorator here, although it will probably kinda fix the failure (because the bot does not have xml support either). I *think* the compressed section support is controlled by presence of zlib.
Since the bot is not immediately broken, I think we can leave bde5d31 in to avoid the churn. Jorge, could you replace the xml thingy with a more appropriate decorator?
Probably either use std::move when passing result_data_sp to SetOpaque, or roll the expressions together (to avoid an unnecessary copy of a ref counted smart pointer, that would cause extra increment/decrement of the ref count)