summaryrefslogtreecommitdiff
path: root/lldb/test/API/python_api/basename/TestGetBaseName.py
AgeCommit message (Collapse)Author
2025-09-04[lldb] Add issue no to xfail decorators in TestGetBaseName (#155939)Muhammad Omair Javaid
TestGetBaseName.py is currently marked as an expected failure on Windows because SBFunction::GetBaseName() and SBSymbol::GetBaseName() don’t yet handle MSVC-style mangling. This patch updates the @expectedFailureAll decorator to include a reference to https://github.com/llvm/llvm-project/issues/156861
2025-09-01[lldb][test] Mark TestGetBaseName.py as expected failure on WindowsMuhammad Omair Javaid
TestGetBaseName.py introduced in PR #155939 is failing on windows LLDB bots. This patch adds @expectedFailureAll(oslist=["windows"]) decorator to mark it as an expected failure on Windows to make buildbots green while the underlying issue is investigated. (see: https://lab.llvm.org/buildbot/#/builders/141/builds/11176).
2025-08-28[lldb] Add SBFunction::GetBaseName() & SBSymbol::GetBaseName() (#155939)Jonas Devlieghere
When you are trying for instance to set a breakpoint on a function by name, but the SBFunction or SBSymbol are returning demangled names with argument lists, that match can be tedious to do. Internally, the base name of a symbol is something we handle all the time, so it's reasonable that there should be a way to get that info from the API as well. rdar://159318791