================ @@ -395,43 +402,56 @@ ExpressionContext DAP::DetectExpressionContext(lldb::SBFrame &frame, case ReplMode::Command: return ExpressionContext::Command; case ReplMode::Auto: - // If the frame is invalid then there is no variables to complete, assume - // this is an lldb command instead. - if (!frame.IsValid()) { - return ExpressionContext::Command; - } - + // To determine if the expression is a command or not, check if the first + // term is a variable or command. If its a variable in scope we will prefer + // that behavior and give a warning to the user if they meant to invoke the + // operation as a command. + // + // Example use case: + // int p and expression "p + 1" > variable + // int i and expression "i" > variable + // int var and expression "va" > command + const auto term = FirstTerm(expression); + auto ci = debugger.GetCommandInterpreter(); lldb::SBCommandReturnObject result; - debugger.GetCommandInterpreter().ResolveCommand(text.data(), result); - - // If this command is a simple expression like `var + 1` check if there is - // a local variable name that is in the current expression. If so, ensure - // the expression runs in the variable context. - lldb::SBValueList variables = frame.GetVariables(true, true, true, true); - llvm::StringRef input = text; - for (uint32_t i = 0; i < variables.GetSize(); i++) { - llvm::StringRef name = variables.GetValueAtIndex(i).GetName(); - // Check both directions in case the input is a partial of a variable - // (e.g. input = `va` and local variable = `var1`). - if (input.contains(name) || name.contains(input)) { - if (!auto_repl_mode_collision_warning) { - llvm::errs() << "Variable expression '" << text - << "' is hiding an lldb command, prefix an expression " - "with '" - << g_dap.command_escape_prefix - << "' to ensure it runs as a lldb command.\n"; - auto_repl_mode_collision_warning = true; - } - return ExpressionContext::Variable; + ci.ResolveCommand(term.c_str(), result); + bool term_is_command = result.Succeeded(); + bool term_is_variable = frame.FindVariable(term.c_str()).IsValid(); + + // If we have both a variable and command, warn the user about the conflict. + if (term_is_command && term_is_variable) { + llvm::errs() + << "warning: Expression '" << term + << "' is both an lldb command and variable, evaluating the " + "expression as a variable. To evaluate the lldb command, use '" ---------------- walter-erquinigo wrote:
```suggestion << "Warning: '" << term << "' is both an LLDB command and variable. It will be " "evaluated as a variable. To evaluate the expression as an LLDB command, use '"... ``` https://github.com/llvm/llvm-project/pull/78005 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits