[all-commits] [llvm/llvm-project] 38dfb2: [lldb] Support debugging utility functions

Jonas Devlieghere via All-commits all-commits at lists.llvm.org
Wed Feb 24 11:36:21 PST 2021


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 38dfb235db19caa1aaa58c1c8153a7464b932087
      https://github.com/llvm/llvm-project/commit/38dfb235db19caa1aaa58c1c8153a7464b932087
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2021-02-24 (Wed, 24 Feb 2021)

  Changed paths:
    M lldb/include/lldb/Expression/UtilityFunction.h
    M lldb/include/lldb/Target/Target.h
    M lldb/source/Expression/FunctionCaller.cpp
    M lldb/source/Expression/UtilityFunction.cpp
    M lldb/source/Plugins/ExpressionParser/Clang/ClangExpressionSourceCode.cpp
    M lldb/source/Plugins/ExpressionParser/Clang/ClangExpressionSourceCode.h
    M lldb/source/Plugins/ExpressionParser/Clang/ClangUtilityFunction.cpp
    M lldb/source/Plugins/ExpressionParser/Clang/ClangUtilityFunction.h
    M lldb/source/Plugins/TypeSystem/Clang/TypeSystemClang.cpp
    M lldb/source/Target/Target.cpp
    M lldb/source/Target/TargetProperties.td

  Log Message:
  -----------
  [lldb] Support debugging utility functions

LLDB uses utility functions to run code in the inferior for its own
internal purposes, such as reading classes from the Objective-C runtime
for example. Because these expressions should be transparent to the
user, we ignore breakpoints and unwind the stack on errors, which
makes them hard to debug.

This patch adds a new setting target.debug-utility-expression that, when
enabled, changes these options to facilitate debugging. It enables
breakpoints, disables unwinding and writes out the utility function
source code to disk so it shows up in the source view.

Differential revision: https://reviews.llvm.org/D97249




More information about the All-commits mailing list