summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/functionalities
diff options
context:
space:
mode:
authorRaphael Isemann <teemperor@gmail.com>2019-07-11 19:26:55 +0000
committerRaphael Isemann <teemperor@gmail.com>2019-07-11 19:26:55 +0000
commit60b71ce0e4f23e2dd73c58c7c0f15df6702ed188 (patch)
tree7a5052a912434623685b0863f17a615246005610 /lldb/packages/Python/lldbsuite/test/functionalities
parenteda5d870e916aedb8d4fe4549a65eb4e04f2b6a7 (diff)
downloadbcm5719-llvm-60b71ce0e4f23e2dd73c58c7c0f15df6702ed188.tar.gz
bcm5719-llvm-60b71ce0e4f23e2dd73c58c7c0f15df6702ed188.zip
[lldb] Don't use __FUNCTION__ as a file name
Summary: I saw while debugging that we call this file `ParseInternal`, which is not a very good name for our fake expression file and also adds this unnecessary link between the way we name this function and the other source location names we get from the expression parser. This patch is renaming it to `<lldb-expr>` which is closer to the way Clang names its buffers, it doesn't depend on the function name (which changes when I refactor this code) and it's easier to grep for. Reviewers: davide Reviewed By: davide Subscribers: abidh, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D64545 llvm-svn: 365812
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud