From 0171866672346f2a6e956ea97d5cc913f85b39db Mon Sep 17 00:00:00 2001 From: Raphael Isemann Date: Wed, 10 Jul 2019 21:04:01 +0000 Subject: [lldb] Fix handling of dollar characters in expr command llvm-svn: 365698 --- .../expression_command/unicode-in-variable/main.cpp | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 lldb/packages/Python/lldbsuite/test/expression_command/unicode-in-variable/main.cpp (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/unicode-in-variable/main.cpp') diff --git a/lldb/packages/Python/lldbsuite/test/expression_command/unicode-in-variable/main.cpp b/lldb/packages/Python/lldbsuite/test/expression_command/unicode-in-variable/main.cpp new file mode 100644 index 00000000000..82e38b1ef4c --- /dev/null +++ b/lldb/packages/Python/lldbsuite/test/expression_command/unicode-in-variable/main.cpp @@ -0,0 +1,17 @@ +// Make sure we correctly handle unicode in variable names. + +struct A { + // We need a member variable in the context that could shadow our local + // variable. If our optimization code fails to handle this, then we won't + // correctly inject our local variable so that it won't get shadowed. + int foob\u00E1r = 2; + int foo() { + int foob\u00E1r = 3; + return foob\u00E1r; //%self.expect("expr foobár", substrs=['(int)', ' = 3']) + } +}; + +int main() { + A a; + return a.foo(); +} -- cgit v1.2.3