[all-commits] [llvm/llvm-project] f58cff: [lldb][Debugger] Register 'testing.XXX' settings w...

[Michael Buch via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: f58cffb27399c2e90958bbc15c14fed841ae4174
      https://github.com/llvm/llvm-project/commit/f58cffb27399c2e90958bbc15c14fed841ae4174
  Author: Michael Buch <michaelbuch12 at gmail.com>
  Date:   2026-03-11 (Wed, 11 Mar 2026)

  Changed paths:
    M lldb/source/Core/Debugger.cpp
    A lldb/test/Shell/Settings/TestTestingSettings.test

  Log Message:
  -----------
  [lldb][Debugger] Register 'testing.XXX' settings with Debugger (#185897)

The `testing.XXX` settings (added in
https://github.com/llvm/llvm-project/pull/177279 and currently just
`testing.inject-variable-location-error`) are supposed to only exist in
asserts builds. However, we never added it as a global property to the
`Debugger`, so the setting wasn't actually usable, in any build.

The one test that did use it [skipped the test on
error](https://github.com/llvm/llvm-project/blob/230e4656170e3764db28b54d91153a1117290171/lldb/test/API/commands/expression/diagnostics/TestExprDiagnostics.py#L286-L288)
as a way to mimick "only run test in asserts mode". However, this just
meant the test never ran.

This patch registers the property and adds a test that ensures an
asserts-LLDB does allow access to it from the CLI.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications