aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/configuration.py
diff options
context:
space:
mode:
authornerix <nerixdev@outlook.de>2025-09-24 16:12:54 +0200
committerGitHub <noreply@github.com>2025-09-24 16:12:54 +0200
commite98f34eb08b2bf7aed787e7f8a7cea9111f044c8 (patch)
tree68b9fbc83e3b55090d3b0c8908f2685ab20c7a4e /lldb/packages/Python/lldbsuite/test/configuration.py
parentfc525bf4229e6e651ad36bade0d82e95d4eeee0d (diff)
downloadllvm-e98f34eb08b2bf7aed787e7f8a7cea9111f044c8.zip
llvm-e98f34eb08b2bf7aed787e7f8a7cea9111f044c8.tar.gz
llvm-e98f34eb08b2bf7aed787e7f8a7cea9111f044c8.tar.bz2
[LLDB][NativePDB] Create functions with mangled name (#149701)
Before, functions created using the NativePDB plugin would not know about their mangled name. This showed when printing a stacktrace. There, only the function name was shown. For https://github.com/llvm/llvm-project/issues/143149, the mangled function name is required to separate different parts. This PR adds that name if available. The Clang AST nodes also take in a mangled name, which was previously unset. I don't think this unblocks anything further, because Clang can mangle the function anyway.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions