github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff origin/main HEAD --extensions cpp --
lldb/unittests/Host/posix/HostTest.cpp
`
Author: Jonas Devlieghere
Date: 2025-10-15T19:52:35-07:00
New Revision: d0d001df99fdd4bf8b727b79c88951d3194e38f6
URL:
https://github.com/llvm/llvm-project/commit/d0d001df99fdd4bf8b727b79c88951d3194e38f6
DIFF:
https://github.com/llvm/llvm-project/commit/d0d001df99fdd4bf8b727b79c88951d3194e38f6.d
https://github.com/naveen-seth edited
https://github.com/llvm/llvm-project/pull/163659
___
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/naveen-seth edited
https://github.com/llvm/llvm-project/pull/163659
___
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -10,8 +10,8 @@
//
//===--===//
-#ifndef LLVM_CLANG_DRIVER_OPTIONUTILS_H
-#define LLVM_CLANG_DRIVER_OPTIONUTILS_H
+#ifndef LLVM_CLANG_OPTIONUTILS_H
+#define LLVM_CLANG_OPTIONUTILS_H
naveen-
https://github.com/naveen-seth edited
https://github.com/llvm/llvm-project/pull/163659
___
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/163292
___
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/ashgti updated
https://github.com/llvm/llvm-project/pull/140777
>From 048b67a1ac5f54f0cbae728b67cf8b6cbbe9ce63 Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Wed, 15 Oct 2025 09:12:13 -0700
Subject: [PATCH] [lldb-dap] Experimenting with async in DAP tests.
This is not fu
@@ -155,15 +152,13 @@ def assertCapabilityIsNotSet(self, key: str, msg:
Optional[str] = None) -> None:
if key in self.dap_server.capabilities:
self.assertEqual(self.dap_server.capabilities[key], False, msg)
-def verify_breakpoint_hit(
-self, br
@@ -1400,6 +1407,9 @@ class Thread : public
std::enable_shared_from_this,
/// The Thread backed by this thread, if any.
lldb::ThreadWP m_backed_thread;
+ /// The Scripted Frame Provider, if any.
+ lldb::ScriptedFrameProviderSP m_frame_provider_sp;
JDevl
https://github.com/qxy11 created
https://github.com/llvm/llvm-project/pull/163653
## Summary:
This change introduces a DAPSessionManager to enable multiple DAP sessions to
share debugger instances when needed, for things like child process debugging
and some scripting hooks that create dynamic
https://github.com/felipepiovezan closed
https://github.com/llvm/llvm-project/pull/163643
___
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Felipe de Azevedo Piovezan
Date: 2025-10-15T14:40:38-07:00
New Revision: a1f233ae07124783b18d9e11351a3e4f7ace05ca
URL:
https://github.com/llvm/llvm-project/commit/a1f233ae07124783b18d9e11351a3e4f7ace05ca
DIFF:
https://github.com/llvm/llvm-project/commit/a1f233ae07124783b18d9e11351a3e4f7
kees wrote:
> You would only get a trap when you get a narrowing conversion, maybe that
> should only be the case for _implicit_ conversions? e.g
> `(int)some_obt_qualified_64bit_type` - I'm not sure I like that as to me it
> feels like the idiomatic casting behaviour would silently truncate,
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: nerix (Nerixyz)
Changes
The `pointers.test` was only run with the DIA plugin. I made the following
changes:
- Remove the check for the function type.
The types of the function are different in the plugins:
```
Native:
Type{0x00010
kees wrote:
tl;dr: I think I understand what you're saying and I think I'm convinced...
We seem to be talking about different things. I'm trying to understand what
you're describing. It looks like you're trying to say that values that are
stored in an OBT variable carry their OB-ness permanent
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: nerix (Nerixyz)
Changes
When creating all types in a compilation unit, simple types (~> primitive
and pointer types) that were only used in function arguments or return types
weren't created as LLDB `Type`s.
With this PR, they're created
@@ -1303,12 +1306,16 @@
PlatformDarwin::LaunchProcess(lldb_private::ProcessLaunchInfo &launch_info) {
lldb_private::Status PlatformDarwin::FindBundleBinaryInExecSearchPaths(
const ModuleSpec &module_spec, Process *process, ModuleSP &module_sp,
-const FileSpecList *mod
https://github.com/JDevlieghere edited
https://github.com/llvm/llvm-project/pull/163479
___
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/jimingham edited
https://github.com/llvm/llvm-project/pull/163471
___
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/rupprecht approved this pull request.
Thanks :)
https://github.com/llvm/llvm-project/pull/163271
___
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/DrSergei updated
https://github.com/llvm/llvm-project/pull/162517
>From 3d548533d38277eb2ba59c810f7634909bb7adbd Mon Sep 17 00:00:00 2001
From: Druzhkov Sergei
Date: Wed, 8 Oct 2025 11:38:55 +0300
Subject: [PATCH 1/2] [lldb-dap] Allow empty memory reference in disassemble
ar
JDevlieghere wrote:
> I love it when I see @skips getting removed
Ha, let's see if it sticks, but I'm optimistic that there's no reason these
test should time out anymore. If they do it's a real issue with `lldb-dap` and
not the test.
https://github.com/llvm/llvm-project/pull/163452
Author: Felipe de Azevedo Piovezan
Date: 2025-10-15T08:02:39-07:00
New Revision: e91786a84967e006b21f2eb0eb59a56b2f925eac
URL:
https://github.com/llvm/llvm-project/commit/e91786a84967e006b21f2eb0eb59a56b2f925eac
DIFF:
https://github.com/llvm/llvm-project/commit/e91786a84967e006b21f2eb0eb59a56b2
rossburton wrote:
The PYTHON_EXECUTABLE and the shebang cleanups are entirely unrelated except by
theme, I can split them it that would make things easier.
https://github.com/llvm/llvm-project/pull/163566
___
lldb-commits mailing list
lldb-commits@lis
DavidSpickett wrote:
And this broke the Python formatter, as in, it failed to parse the code.
Probably one of the infrequently changed projects like Polly has some strange
code in it. Point is - we know this isn't changing actual Python code so ignore
it.
https://github.com/llvm/llvm-project/
DavidSpickett wrote:
I'm not clear on the specific purpose here:
> Ensure that the nested native CMake build uses the same Python interpreter as
> the outer build.
>
> Unify python shebangs so that they use python3 everywhere, instead of a mix
> of python and python3.
Is the first implemented
felipepiovezan wrote:
Addressed review comments
https://github.com/llvm/llvm-project/pull/162675
___
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -735,6 +735,56 @@ This is a performance optimization, which speeds up
debugging by avoiding
multiple round-trips for retrieving thread information. The information from
this
packet can be retrieved using a combination of `qThreadStopInfo` and `m`
packets.
+### MultiMemRe
@@ -735,6 +735,56 @@ This is a performance optimization, which speeds up
debugging by avoiding
multiple round-trips for retrieving thread information. The information from
this
packet can be retrieved using a combination of `qThreadStopInfo` and `m`
packets.
+### MultiMemRe
ojhunt wrote:
> @JustinStitt were looking over things, and I stumbled over something here...
>
> > Thanks. So IIUC, the rule is:
> >
> > 1. If the type of either operand of an arithmetic operator is `__ob_trap`,
> > the operator traps on overflow, and the result type is `__ob_trap`.
>
> This
@@ -15,10 +15,23 @@ class FinishFromEmptyFunctionTestCase(TestBase):
def test_finish_from_empty_function(self):
"""Test that when stopped at a breakpoint in an empty function, finish
leaves it correctly."""
self.build()
-exe = self.getBuildArtifact(
Author: aokblast
Date: 2025-10-15T09:55:00+01:00
New Revision: c9b07f34d46237ea547f379f979e7d0106e5a910
URL:
https://github.com/llvm/llvm-project/commit/c9b07f34d46237ea547f379f979e7d0106e5a910
DIFF:
https://github.com/llvm/llvm-project/commit/c9b07f34d46237ea547f379f979e7d0106e5a910.diff
LOG:
@@ -735,6 +735,56 @@ This is a performance optimization, which speeds up
debugging by avoiding
multiple round-trips for retrieving thread information. The information from
this
packet can be retrieved using a combination of `qThreadStopInfo` and `m`
packets.
+### MultiMemRe
@@ -735,6 +735,56 @@ This is a performance optimization, which speeds up
debugging by avoiding
multiple round-trips for retrieving thread information. The information from
this
packet can be retrieved using a combination of `qThreadStopInfo` and `m`
packets.
+### MultiMemRe
@@ -735,6 +735,56 @@ This is a performance optimization, which speeds up
debugging by avoiding
multiple round-trips for retrieving thread information. The information from
this
packet can be retrieved using a combination of `qThreadStopInfo` and `m`
packets.
+### MultiMemRe
https://github.com/DavidSpickett approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/163249
___
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Nerixyz wrote:
If I see it correctly, then this check is for sorting functions. Do you have a
full backtrace?
https://github.com/llvm/llvm-project/pull/156250
___
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mai
38 matches
Mail list logo
