https://github.com/frederick-vs-ja closed
https://github.com/llvm/llvm-project/pull/142516
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: A. Jiang
Date: 2025-07-03T13:57:20+08:00
New Revision: 119705e5ad2b7e4bfc55f7df9a8fbaa7504aedbd
URL:
https://github.com/llvm/llvm-project/commit/119705e5ad2b7e4bfc55f7df9a8fbaa7504aedbd
DIFF:
https://github.com/llvm/llvm-project/commit/119705e5ad2b7e4bfc55f7df9a8fbaa7504aedbd.diff
LOG:
HemangGadhavi wrote:
> @HemangGadhavi (can't add you to reviewers for whatever reason)
May be I do not have maintainer access yet ..?? Not sure.
https://github.com/llvm/llvm-project/pull/146686
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
@@ -420,8 +420,7 @@ void DWARFFormValue::Dump(Stream &s) const {
DumpAddress(s.AsRawOstream(), uvalue, sizeof(uint64_t) * 2);
else
DumpAddress(s.AsRawOstream(), uvalue,
HemangGadhavi wrote:
No need to check for the <= 2 DWARF version now, Becau
@@ -53,6 +54,30 @@ bool DWARFExpressionList::ContainsAddress(lldb::addr_t
func_load_addr,
return GetExpressionAtAddress(func_load_addr, addr) != nullptr;
}
+std::optional
+DWARFExpressionList::GetExpressionEntryAtAddress(lldb::addr_t func_load_addr,
+
https://github.com/UltimateForce21 updated
https://github.com/llvm/llvm-project/pull/144238
>From 8ed8c540e7600d720a63bc2882a81a2c65c11d41 Mon Sep 17 00:00:00 2001
From: ultimateforce21
Date: Wed, 11 Jun 2025 00:11:09 -0400
Subject: [PATCH 01/11] [lldb] Add DWARFExpressionEntry and
GetExpressi
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Alexandre Perez (aperez)
Changes
It looks like #146603 broke the
[lldb-remote-linux-win](https://lab.llvm.org/buildbot/#/builders/197) build bot
because `MCPUnixSocketCommandTestCase` is trying to start a protocol-server via
unix domain s
https://github.com/aperez created
https://github.com/llvm/llvm-project/pull/146807
It looks like #146603 broke the
[lldb-remote-linux-win](https://lab.llvm.org/buildbot/#/builders/197) build bot
because `MCPUnixSocketCommandTestCase` is trying to start a protocol-server via
unix domain socket
https://github.com/kusmour approved this pull request.
https://github.com/llvm/llvm-project/pull/146807
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -253,30 +436,35 @@ _LIBCPP_CONSTEXPR_SINCE_CXX20 void __split_buffer<_Tp,
_Allocator>::__construct_
template
_LIBCPP_CONSTEXPR_SINCE_CXX20 void
__split_buffer<_Tp, _Allocator>::__construct_at_end(size_type __n,
const_reference __x) {
- _ConstructTransaction __tx(std::add
cjdb wrote:
I still think that `_LIBCPP_SIZE_BASED_VECTOR` is the most appropriate name,
since this work was entirely motivated by size-based vector, and this PR is a
precursor to enabling size-based vector in libc++. The changes to `std::deque`
are only happ
@@ -431,52 +599,61 @@ _LIBCPP_CONSTEXPR_SINCE_CXX20 void __split_buffer<_Tp,
_Allocator>::shrink_to_fi
template
template
_LIBCPP_CONSTEXPR_SINCE_CXX20 void __split_buffer<_Tp,
_Allocator>::emplace_front(_Args&&... __args) {
- if (__begin_ == __first_) {
-if (__end_ < _
@@ -78,23 +80,232 @@ public:
__split_buffer,
void>;
- pointer __first_;
- pointer __begin_;
- pointer __end_;
- _LIBCPP_COMPRESSED_PAIR(pointer, __cap_, allocator_type, __alloc_);
+ struct __data {
cjdb wrote:
https://github.com/Jlalond edited
https://github.com/llvm/llvm-project/pull/146777
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Jlalond updated
https://github.com/llvm/llvm-project/pull/146777
>From d17473cc32acb31935759012ca87342d750d68f7 Mon Sep 17 00:00:00 2001
From: Jacob Lalonde
Date: Wed, 2 Jul 2025 09:18:59 -0700
Subject: [PATCH 1/8] Fix logs, prevent accidentally printing a partial read
when
github-actions[bot] wrote:
:warning: Python code formatter, darker found issues in your code. :warning:
You can test this locally with the following command:
``bash
darker --check --diff -r HEAD~1...HEAD
lldb/test/API/functionalities/process_save_core_minidump/TestProcessSaveCore
https://github.com/Jlalond edited
https://github.com/llvm/llvm-project/pull/146777
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Jlalond edited
https://github.com/llvm/llvm-project/pull/146777
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Jacob Lalonde (Jlalond)
Changes
### Context
Over a year ago, I landed support for 64b Memory ranges in Minidump (#95312). In this patch we added the Memory64 list stream, which is
effectively a Linked List on disk. The layout is a sixteen
https://github.com/Jlalond created
https://github.com/llvm/llvm-project/pull/146777
### Context
Over a year ago, I landed support for 64b Memory ranges in Minidump (#95312).
In this patch we added the Memory64 list stream, which is effectively a Linked
List on disk. The layout is a sixteen by
chelcassanova wrote:
For the include problem, `cstdint` isn't in the Clang resource directory that
gets passed in. maybe a system include dir must also be passed in here. One
thing I'm confused about is that the tool is built and run correctly in the
actual CMake build phase.
https://github.c
https://github.com/ashgti converted_to_draft
https://github.com/llvm/llvm-project/pull/146754
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
ashgti wrote:
We can add a button to the variables UI or a context menu entry for running the
description. I can switch to that instead.
https://github.com/llvm/llvm-project/pull/146754
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https:/
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: John Harrison (ashgti)
Changes
This partially fixes https://github.com/llvm/llvm-project/issues/146559.
When hovering over variables while debugging with lldb-dap we are receiving
hover requests that include symbols.
For example, if you h
https://github.com/ashgti ready_for_review
https://github.com/llvm/llvm-project/pull/146773
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/ashgti edited
https://github.com/llvm/llvm-project/pull/146773
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/ashgti created
https://github.com/llvm/llvm-project/pull/146773
This partially fixes https://github.com/llvm/llvm-project/issues/146559.
When hovering over variables while debugging with lldb-dap we are receiving
hover requests that include symbols.
For example, if you have
jimingham wrote:
There are exceptions to this, for instance we run functions automatically to
gather the various Sanitizer report results. But those functions have been
written with this use in mind, so they don't take locks or do anything that
might be unsafe.
https://github.com/llvm/llvm-p
jimingham wrote:
Remember, running code is NOT a risk free operation.
If I am stopped on a thread in code that has acquired a non-recursive lock A,
and I run an expression by hand that ends up first successfully acquiring a
lock B and then trying to acquire A, that expression will deadlock. T
chelcassanova wrote:
> I expect not because the compilation database only deals with sources, .cpp,
> .cc etc. not headers.
So it should be trying to load something like `compile_commands.json`? Which is
in the root of the build dir so when the tool needs to load it's going to try
and do some
jimingham wrote:
Also note that for ObjC in particular for many classes the "Object Description"
is NOT a summary of the object. Print the Object Description of an
NSDictionary 1000 objects and you'll get pages and pages of output with all the
elements (and their Descriptions inline IIRC). T
jimingham wrote:
IIRC, C# has a similar object description mechanism, and they had to add some
annotations to the object to specify "don't run this one automatically" because
they kept getting into trouble with object descriptions that did too much work,
or forced lazily evaluated entities to
jimingham wrote:
The way Xcode deals with this is that the Locals view's Right-Click menu offers
a "Print Description" action. That way users can very easily dial up the
object description, but doing so remains under the user's explicit control.
https://github.com/llvm/llvm-project/pull/14675
jimingham wrote:
Object Description is always code-running. It works in languages that have a
convention for printing a user-facing string representation of an object. I
guess you could have a language with a static way to do this but I haven't seen
one.
https://github.com/llvm/llvm-project
jimingham wrote:
dynamic value and object description are orthogonal. Dynamic value is the
system that allows you to discover, for instance, the "most specific class of
an object" when you are passed a pointer typed as one of the base classes of
that most specific class. , I don't think
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `publish-sphinx-docs`
running on `as-worker-4` while building `lldb,llvm` at step 5
"build-docs-llvm-html-docs-clang-html-docs-clang...".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/45/builds/13922
ashgti wrote:
> If you can ensure that the expression you are running can safely be executed
> by running only the current thread, it's only a performance problem to run
> expressions behind the user's back. But otherwise, we really should only run
> expressions when the user explicitly asks u
https://github.com/JDevlieghere updated
https://github.com/llvm/llvm-project/pull/146602
>From 656beb2df5f39604454af0e3f4a9f4b1b7e9c5f8 Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere
Date: Tue, 1 Jul 2025 16:02:21 -0700
Subject: [PATCH 1/5] [lldb] Add SB API to make a breakpoint a hardware
b
https://github.com/ashgti closed
https://github.com/llvm/llvm-project/pull/146632
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: John Harrison
Date: 2025-07-02T12:49:19-07:00
New Revision: d457621872528d27c8081cf147d41a6f46276d1d
URL:
https://github.com/llvm/llvm-project/commit/d457621872528d27c8081cf147d41a6f46276d1d
DIFF:
https://github.com/llvm/llvm-project/commit/d457621872528d27c8081cf147d41a6f46276d1d.diff
https://github.com/mstorsjo approved this pull request.
This fixes compilation on 64 bit mingw for me at least.
https://github.com/llvm/llvm-project/pull/146632
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/ma
Author: Jonas Devlieghere
Date: 2025-07-02T12:07:20-07:00
New Revision: ab0fa6c5dc725ef6f839ac8cea9b3a41aa3a5b75
URL:
https://github.com/llvm/llvm-project/commit/ab0fa6c5dc725ef6f839ac8cea9b3a41aa3a5b75
DIFF:
https://github.com/llvm/llvm-project/commit/ab0fa6c5dc725ef6f839ac8cea9b3a41aa3a5b75.d
jimingham wrote:
I'm not sure that you really always want to do this. Fetching the
ObjectDescription for a variable means running code in the target to do so.
And because we can't tell whether code in an ObjectDescription will require
locks that other threads might hold, we do our usual "try
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: John Harrison (ashgti)
Changes
This corrects a mistake I made when I previously tried to add support for
obj-c/swift variables in lldb-dap. This should call into `GetObjectDescription`
if there is no summary of the type available and the d
https://github.com/ashgti ready_for_review
https://github.com/llvm/llvm-project/pull/146754
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/ashgti created
https://github.com/llvm/llvm-project/pull/146754
This corrects a mistake I made when I previously tried to add support for
obj-c/swift variables in lldb-dap. This should call into `GetObjectDescription`
if there is no summary of the type available and the desc
Author: Jason Molenda
Date: 2025-07-02T11:16:04-07:00
New Revision: 00e071d6906246192b344f3e28d9e15a0e0faf68
URL:
https://github.com/llvm/llvm-project/commit/00e071d6906246192b344f3e28d9e15a0e0faf68
DIFF:
https://github.com/llvm/llvm-project/commit/00e071d6906246192b344f3e28d9e15a0e0faf68.diff
Author: Jason Molenda
Date: 2025-07-02T10:21:38-07:00
New Revision: dfcef35ff1d30d112362645ec2cd0d5e99952b0f
URL:
https://github.com/llvm/llvm-project/commit/dfcef35ff1d30d112362645ec2cd0d5e99952b0f
DIFF:
https://github.com/llvm/llvm-project/commit/dfcef35ff1d30d112362645ec2cd0d5e99952b0f.diff
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-remote-linux-ubuntu`
running on `as-builder-9` while building `lldb,llvm` at step 7 "build-default".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/195/builds/11272
Here is the relevant piece of
JDevlieghere wrote:
Closing in favor of https://github.com/llvm/llvm-project/pull/146578
https://github.com/llvm/llvm-project/pull/146435
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-com
https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/146435
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
jimingham wrote:
It would be good to test the response to enabling a HW breakpoint or trying to
set it to HW when you've exhausted the number of HW breakpoint resources. For
some reason we have SBProcess::GetNumSupportedHardwareWatchpoints but not
SBProcess::GetNumSupportedHardwareBreakpoints
https://github.com/jasonmolenda closed
https://github.com/llvm/llvm-project/pull/146480
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
aperez wrote:
@kusmour @JDevlieghere
I added a test for this. Since my change is in command parsing I created a test
in `lldb/test/API/commands/protocol/` rather than extend
`lldb/unittests/Protocol/ProtocolMCPServerTest.cpp`. LMK what you think.
https://github.com/llvm/llvm-project/pull/1466
https://github.com/aperez updated
https://github.com/llvm/llvm-project/pull/146603
>From 8ffabe86dd320880736c691e45e71611988ceb38 Mon Sep 17 00:00:00 2001
From: Alexandre Perez
Date: Tue, 1 Jul 2025 14:19:45 -0700
Subject: [PATCH 1/2] [lldb][mcp] Fix unix domain socket protocol server
addresse
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/146740
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
adrian-prantl wrote:
More test coverage sounds great!
https://github.com/llvm/llvm-project/pull/146740
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/adrian-prantl approved this pull request.
https://github.com/llvm/llvm-project/pull/146740
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
JDevlieghere wrote:
@labath let me know what you think of this approach. I'd like to take this on
the Swift 6.2 release branch as it addresses several issues folks have reported.
https://github.com/llvm/llvm-project/pull/146578
___
lldb-commits mailin
https://github.com/JDevlieghere approved this pull request.
👋
https://github.com/llvm/llvm-project/pull/146480
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/JDevlieghere updated
https://github.com/llvm/llvm-project/pull/146602
>From 656beb2df5f39604454af0e3f4a9f4b1b7e9c5f8 Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere
Date: Tue, 1 Jul 2025 16:02:21 -0700
Subject: [PATCH 1/4] [lldb] Add SB API to make a breakpoint a hardware
b
jimingham wrote:
There's one more tricky bit we need to handle here. What happens if I have a
breakpoint that has more locations than we have hardware resources, and you do
`SBBreakpoint.SetIsHardware(True)`? Do we set the first `n` breakpoints and
stop there? Do we back out and restore the
https://github.com/JDevlieghere updated
https://github.com/llvm/llvm-project/pull/146602
>From 656beb2df5f39604454af0e3f4a9f4b1b7e9c5f8 Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere
Date: Tue, 1 Jul 2025 16:02:21 -0700
Subject: [PATCH 1/3] [lldb] Add SB API to make a breakpoint a hardware
b
@@ -69,7 +69,7 @@ class BreakpointLocation
// The next section deals with various breakpoint options.
/// If \a enabled is \b true, enable the breakpoint, if \b false disable it.
- void SetEnabled(bool enabled);
+ bool SetEnabled(bool enabled);
jimingham
@@ -148,6 +148,8 @@ class LLDB_API SBBreakpoint {
bool IsHardware() const;
+ bool SetIsHardware(bool is_hardware);
jimingham wrote:
Document the return value's meaning somewhere.
https://github.com/llvm/llvm-project/pull/146602
__
@@ -0,0 +1,120 @@
+# coding=utf8
+"""
+Test std::*string summaries with MSVC's STL.
+"""
Michael137 wrote:
https://github.com/llvm/llvm-project/pull/146740
https://github.com/llvm/llvm-project/pull/143177
___
lldb-comm
@@ -0,0 +1,15 @@
+# Disabling until the lldb-rpc-gen tool lands.
+UNSUPPORTED: system-windows, system-linux, system-darwin
chelcassanova wrote:
The unsupported can probably be removed actually, these tests still need to
test after the tool lands however.
https:
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/146740
>From 66a4fdb156d493bf994fd5c0050cfd2d7352732d Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 2 Jul 2025 15:01:27 +0100
Subject: [PATCH 1/3] [lldb][test] Turn (most) libcxx data-formatters tests
into
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Michael Buch (Michael137)
Changes
This patch moves all the data-formatter tests that were only run for libc++ to
the generic directory. There's nothing libc++ specific about these tests. For
aynthing tied to libcxx we can have a dedicated
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 HEAD~1 HEAD --extensions cpp --
lldb/test/API/functionalities/data-formatter/data-for
github-actions[bot] wrote:
:warning: Python code formatter, darker found issues in your code. :warning:
You can test this locally with the following command:
``bash
darker --check --diff -r HEAD~1...HEAD
lldb/test/API/functionalities/data-formatter/data-formatter-stl/generic/rang
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/146740
>From 66a4fdb156d493bf994fd5c0050cfd2d7352732d Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 2 Jul 2025 15:01:27 +0100
Subject: [PATCH] [lldb][test] Turn (most) libcxx data-formatters tests into
gen
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/146740
>From 8e2f7ff404eaf048179ad43b65d53ef1617cefb9 Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 2 Jul 2025 15:01:27 +0100
Subject: [PATCH] [lldb][test] Turn (most) libcxx data-formatters tests into
gen
https://github.com/Michael137 created
https://github.com/llvm/llvm-project/pull/146740
This patch moves all the data-formatter tests that were only run for libc++ to
the generic directory. There's nothing libc++ specific about these tests. For
aynthing tied to libcxx we can have a dedicated su
https://github.com/JDevlieghere approved this pull request.
https://github.com/llvm/llvm-project/pull/146603
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
ashgti wrote:
I'll update my PR to add `#include `
https://github.com/llvm/llvm-project/pull/145621
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/UltimateForce21 updated
https://github.com/llvm/llvm-project/pull/144238
>From 8ed8c540e7600d720a63bc2882a81a2c65c11d41 Mon Sep 17 00:00:00 2001
From: ultimateforce21
Date: Wed, 11 Jun 2025 00:11:09 -0400
Subject: [PATCH 01/10] [lldb] Add DWARFExpressionEntry and
GetExpressi
https://github.com/ashgti updated
https://github.com/llvm/llvm-project/pull/146632
>From 3e0129934a74f9300a7d386797b63304a02b855f Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Tue, 1 Jul 2025 20:55:32 -0700
Subject: [PATCH 1/3] [lldb] Fixing warnings / win32 builds in MainLoop.
Commit 1a7
https://github.com/ashgti updated
https://github.com/llvm/llvm-project/pull/146632
>From 3e0129934a74f9300a7d386797b63304a02b855f Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Tue, 1 Jul 2025 20:55:32 -0700
Subject: [PATCH 1/2] [lldb] Fixing warnings / win32 builds in MainLoop.
Commit 1a7
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Michael Buch (Michael137)
Changes
The plan is to move all STL formatter API tests into a single directory.
The `std::deque` test is currently the only test that is duplicated between the
`libcxx` and `generic` directories. This patch moves
https://github.com/Michael137 closed
https://github.com/llvm/llvm-project/pull/146697
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Michael Buch
Date: 2025-07-02T16:05:09+01:00
New Revision: e32439249d8af2b1d0654e01472506d7e0c92f7b
URL:
https://github.com/llvm/llvm-project/commit/e32439249d8af2b1d0654e01472506d7e0c92f7b
DIFF:
https://github.com/llvm/llvm-project/commit/e32439249d8af2b1d0654e01472506d7e0c92f7b.diff
https://github.com/adrian-prantl approved this pull request.
https://github.com/llvm/llvm-project/pull/146697
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
DavidSpickett wrote:
Also it's a bit misleading, this is printed but I don't know if it is the cause
of the include problem:
```
fixed-compilation-database: Error while opening fixed database: No such file or
directory
json-compilation-database: Error while opening JSON database: No such file o
github-actions[bot] wrote:
:warning: Python code formatter, darker found issues in your code. :warning:
You can test this locally with the following command:
``bash
darker --check --diff -r HEAD~1...HEAD
lldb/test/API/functionalities/data-formatter/data-formatter-stl/generic/dequ
DavidSpickett wrote:
> I'm still seeing the no job control error in the pre-commit CI. As far as I
> know this error is not supposed to be happening, RPC should be getting built
> which should mean that the lldb-rpc-gen tool is available for use in the
> shell test. I can't repro locally, I'm
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/146697
>From 168f2c960757ad0203391724836d021b8bf89b5b Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 2 Jul 2025 14:51:04 +0100
Subject: [PATCH 1/2] [lldb][test] Consolidate generic and libcxx std::deque
for
https://github.com/Michael137 created
https://github.com/llvm/llvm-project/pull/146697
The plan is to move all STL formatter API tests into a single directory.
The `std::deque` test is currently the only test that is duplicated between the
`libcxx` and `generic` directories. This patch moves t
Author: Michael Buch
Date: 2025-07-02T14:36:41+01:00
New Revision: fc00256b2b4d7a5328b775b51240258e0d28701c
URL:
https://github.com/llvm/llvm-project/commit/fc00256b2b4d7a5328b775b51240258e0d28701c
DIFF:
https://github.com/llvm/llvm-project/commit/fc00256b2b4d7a5328b775b51240258e0d28701c.diff
DavidSpickett wrote:
@HemangGadhavi (can't add you to reviewers for whatever reason)
https://github.com/llvm/llvm-project/pull/146686
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: David Spickett (DavidSpickett)
Changes
Not that we ever do that, because this is unused code, but if someone was
debugging lldb I guess they'd call this.
Was missed in https://github.com/llvm/llvm-project/pull/145645
Relates to https://gi
https://github.com/DavidSpickett created
https://github.com/llvm/llvm-project/pull/146686
Not that we ever do that, because this is unused code, but if someone was
debugging lldb I guess they'd call this.
Was missed in https://github.com/llvm/llvm-project/pull/145645
Relates to https://github
smithp35 wrote:
> Just requesting changes so we don't forget about the ABI change.
>
> Might need to coordinate with other toolchains, we can deal with that after
> ABI discussions.
I did a quick check of the support for R_AARCH64_TLS_DTPREL64 in GNU by making
up a fake .debug_info section wi
https://github.com/da-viper closed
https://github.com/llvm/llvm-project/pull/145231
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: DrSergei
Date: 2025-07-02T12:16:48+01:00
New Revision: 5fe63ae9a3fb7502ce7ed076ea14def97d79e85e
URL:
https://github.com/llvm/llvm-project/commit/5fe63ae9a3fb7502ce7ed076ea14def97d79e85e
DIFF:
https://github.com/llvm/llvm-project/commit/5fe63ae9a3fb7502ce7ed076ea14def97d79e85e.diff
LOG:
mstorsjo wrote:
> They put up #146632 to fix it, if one of you wants to check it works.
Thanks - it looks like that does fix some issues, but it only lets the build
proceed slightly further to hit other errors caused by this patch:
```
../../lldb/source/Host/windows/MainLoopWindows.cpp:120:3: e
https://github.com/da-viper updated
https://github.com/llvm/llvm-project/pull/143644
>From 24e8bbe12758773ef9ca55c3c4022a610db434e9 Mon Sep 17 00:00:00 2001
From: Ebuka Ezike
Date: Wed, 11 Jun 2025 02:14:12 +0100
Subject: [PATCH 1/2] [lldb-dap] Prevent using an implicit `step-in`.
When there i
https://github.com/Michael137 closed
https://github.com/llvm/llvm-project/pull/146562
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: nerix
Date: 2025-07-02T11:21:31+01:00
New Revision: 4c7a706589ca97101972c88d90449d27275b3ab5
URL:
https://github.com/llvm/llvm-project/commit/4c7a706589ca97101972c88d90449d27275b3ab5
DIFF:
https://github.com/llvm/llvm-project/commit/4c7a706589ca97101972c88d90449d27275b3ab5.diff
LOG: [L
Author: Michael Buch
Date: 2025-07-02T11:21:02+01:00
New Revision: 40275a4ee31203b9ed014b0b830f456a1c267063
URL:
https://github.com/llvm/llvm-project/commit/40275a4ee31203b9ed014b0b830f456a1c267063
DIFF:
https://github.com/llvm/llvm-project/commit/40275a4ee31203b9ed014b0b830f456a1c267063.diff
1 - 100 of 115 matches
Mail list logo
