[all-commits] [llvm/llvm-project] 5c78be: [LLDB] Add a target.launch-working-dir setting

[Walter Erquinigo via All-commits]

  Branch: refs/heads/users/walter-erquinigo/run
  Home:   https://github.com/llvm/llvm-project
  Commit: 5c78bec1620a4cb6c3aa1b8c097b68fc9aa97254
      https://github.com/llvm/llvm-project/commit/5c78bec1620a4cb6c3aa1b8c097b68fc9aa97254
  Author: walter erquinigo <walter at modular.com>
  Date:   2024-11-04 (Mon, 04 Nov 2024)

  Changed paths:
    M lldb/include/lldb/Target/Target.h
    M lldb/source/Commands/CommandObjectProcess.cpp
    M lldb/source/Commands/Options.td
    M lldb/source/Target/Target.cpp
    M lldb/source/Target/TargetProperties.td
    M lldb/test/API/commands/process/launch/TestProcessLaunch.py
    M llvm/docs/ReleaseNotes.md

  Log Message:
  -----------
  [LLDB] Add a target.launch-working-dir setting

Internally we use bazel in a way in which it can drop you in a LLDB session with the target launched in a particular cwd, which is needed for things to work. We've been making this automation work via `process launch -w`. However, if later the user wants to restart the process with `r`, then they end up using a different cwd for relaunching the process.
As a way to fix this, I'm adding a target-level setting that allows setting a default cwd used for launching the process without needing the user to specify it manually.



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