[Lldb-commits] [lldb] [debugserver] Migrate MachProcess away from PThreadMutex (NFC) (PR #137553)

2025-04-27 Thread Jonas Devlieghere via lldb-commits
https://github.com/JDevlieghere created https://github.com/llvm/llvm-project/pull/137553 The debugserver code predates modern C++, but with C++11 and later there's no need to have something like PThreadMutex. This migrates MachProcess away from PThreadMutex in preparation for removing it. >Fr

[Lldb-commits] [lldb] [debugserver] Migrate MachProcess away from PThreadMutex (NFC) (PR #137553)

2025-04-27 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Jonas Devlieghere (JDevlieghere) Changes The debugserver code predates modern C++, but with C++11 and later there's no need to have something like PThreadMutex. This migrates MachProcess away from PThreadMutex in preparation for removing i

[Lldb-commits] [lldb] [debugserver] Remove PThreadMutex (NFC) (PR #137555)

2025-04-27 Thread Jonas Devlieghere via lldb-commits
https://github.com/JDevlieghere created https://github.com/llvm/llvm-project/pull/137555 Now that all uses of PThreadMutex have been migrated to their C++ equivalent, this PR removes PThreadMutex itself. >From 1095cfe9cfc0664784884089e52ee50b3976ad4c Mon Sep 17 00:00:00 2001 From: Jonas Devlie

[Lldb-commits] [lldb] [debugserver] Remove PThreadMutex (NFC) (PR #137555)

2025-04-27 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Jonas Devlieghere (JDevlieghere) Changes Now that all uses of PThreadMutex have been migrated to their C++ equivalent, this PR removes PThreadMutex itself. --- Full diff: https://github.com/llvm/llvm-project/pull/137555.diff 9 Files Affe

[Lldb-commits] [lldb] [debugserver] Migrate PThreadEvent away from PThreadMutex (NFC) (PR #137554)

2025-04-27 Thread Jonas Devlieghere via lldb-commits
https://github.com/JDevlieghere created https://github.com/llvm/llvm-project/pull/137554 The debugserver code predates modern C++, but with C++11 and later there's no need to have something like PThreadMutex. This migrates PThreadEvent away from PThreadMutex in preparation for removing it. >F

[Lldb-commits] [lldb] [debugserver] Migrate PThreadEvent away from PThreadMutex (NFC) (PR #137554)

2025-04-27 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Jonas Devlieghere (JDevlieghere) Changes The debugserver code predates modern C++, but with C++11 and later there's no need to have something like PThreadMutex. This migrates PThreadEvent away from PThreadMutex in preparation for removing

[Lldb-commits] [lldb] [lldb][docs] Document new frame-format variables (PR #137522)

2025-04-27 Thread Michael Buch via lldb-commits
https://github.com/Michael137 updated https://github.com/llvm/llvm-project/pull/137522 >From 2388b0951a3e9b0e2ebd297881f17423c8d68b4e Mon Sep 17 00:00:00 2001 From: Michael Buch Date: Sun, 27 Apr 2025 11:23:20 +0100 Subject: [PATCH 1/3] [lldb][docs] Document new frame-format variables --- lld

[Lldb-commits] [lldb] [llvm] [lldb-dap] migrate set breakpoint requests (PR #137448)

2025-04-27 Thread Ely Ronnen via lldb-commits
@@ -322,6 +323,186 @@ enum SteppingGranularity : unsigned { bool fromJSON(const llvm::json::Value &, SteppingGranularity &, llvm::json::Path); +/// Information about a breakpoint created in `setBreakpoints`, +/// `setFunctionBreakpoints`, `setInstructionBreakpoin

[Lldb-commits] [lldb] [llvm] [lldb-dap] migrate set breakpoint requests (PR #137448)

2025-04-27 Thread Ely Ronnen via lldb-commits
@@ -322,6 +323,186 @@ enum SteppingGranularity : unsigned { bool fromJSON(const llvm::json::Value &, SteppingGranularity &, llvm::json::Path); +/// Information about a breakpoint created in `setBreakpoints`, +/// `setFunctionBreakpoints`, `setInstructionBreakpoin

[Lldb-commits] [lldb] [lldb-dap] Mitigate a build error on Windows. (PR #137388)

2025-04-27 Thread Pavel Labath via lldb-commits
labath wrote: > Weird, I wonder what the protected member is that the error is talking about. > Anyway, this seems fine. > 'llvm::Error::Error' It's the default constructor. I guess the implementation tries to default construct the object on some (maybe not dynamically reachable) code path.

<    1   2