[all-commits] [llvm/llvm-project] e4d6ed: [lldb] [llgs] Include process id in W/X stop reasons

[Michał Górny via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: e4d6ed58a86edc339ae124b74668b600f2a0f6d5
      https://github.com/llvm/llvm-project/commit/e4d6ed58a86edc339ae124b74668b600f2a0f6d5
  Author: Michał Górny <mgorny at moritz.systems>
  Date:   2022-06-20 (Mon, 20 Jun 2022)

  Changed paths:
    M lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp
    M lldb/test/API/tools/lldb-server/TestGdbRemoteFork.py

  Log Message:
  -----------
  [lldb] [llgs] Include process id in W/X stop reasons

Include the process identifier in W/X stop reasons when multiprocess
extensions are enabled.

The LLDB client does not support process identifiers there at the moment
but it parses packets in such a way that their presence does not cause
any problems.

Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.llvm.org/D127191


  Commit: ac570fbb8521a31a1931cc070e1b259fcac6a30f
      https://github.com/llvm/llvm-project/commit/ac570fbb8521a31a1931cc070e1b259fcac6a30f
  Author: Michał Górny <mgorny at moritz.systems>
  Date:   2022-06-20 (Mon, 20 Jun 2022)

  Changed paths:
    M lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerLLGS.cpp
    M lldb/test/API/tools/lldb-server/TestGdbRemoteFork.py

  Log Message:
  -----------
  [lldb] [llgs] Include process ID in stop responses

Include the process identifier in the `T` stop responses when
multiprocess extension is enabled (i.e. prepend it to the thread
identifier).  Use the exposed identifier to simplify the fork-and-follow
tests.

The LLDB client accounts for the possible PID since the multiprocess
extension support was added in b601c6719226fb83c43dae62a581e5ee08bfb169.

Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.llvm.org/D127192


Compare: https://github.com/llvm/llvm-project/compare/7cd1c01c8e85...ac570fbb8521