@@ -0,0 +1,103 @@
+import * as vscode from "vscode";
+import * as child_process from "child_process";
+import * as util from "util";
+import { LLDBDapServer } from "./lldb-dap-server";
+import { createDebugAdapterExecutable } from "./debug-adapter-factory";
+import { ConfigureButt
https://github.com/da-viper closed
https://github.com/llvm/llvm-project/pull/131683
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/133078
>From 91110b85aab9ddf41d1b52b9fc23d68883966b93 Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 26 Mar 2025 13:20:24 +
Subject: [PATCH 1/2] [lldb][Target] Clear selected frame index after a
StopInf
https://github.com/JDevlieghere approved this pull request.
https://github.com/llvm/llvm-project/pull/133785
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -778,28 +817,121 @@ llvm::Error DAP::Disconnect(bool terminateDebuggee) {
return ToError(error);
}
+bool DAP::IsCancelled(const protocol::Request &req) {
+ std::lock_guard lock(m_cancelled_requests_mutex);
+ return m_cancelled_requests.contains(req.seq);
+}
+
+void DAP:
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-remote-linux-win`
running on `as-builder-10` while building `lldb` at step 17
"test-check-lldb-api".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/197/builds/2978
Here is the relevant piece of
@@ -0,0 +1,130 @@
+import * as child_process from "node:child_process";
+import * as vscode from "vscode";
+
+function areArraysEqual(lhs: T[], rhs: T[]): boolean {
+ if (lhs.length !== rhs.length) {
+return false;
+ }
+ for (let i = 0; i < lhs.length; i++) {
+if (lhs[i
rupprecht wrote:
Still seeing a crash even with the latest fix applied
```
assertion failed at clang/include/clang/AST/Type.h:945 in const
ExtQualsTypeCommonBase *clang::QualType::getCommonPtr() const: !isNull() &&
"Cannot retrieve a NULL type pointer"
*** Check failure stack trace: ***
@
https://github.com/JDevlieghere edited
https://github.com/llvm/llvm-project/pull/130169
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
santhoshe447 wrote:
> There is another Pull Request for the same functionality #108036. The other
> PR seems to be outdated, though, and this PR seems to be further along (e.g.
> it also has test cases). CC @jennphilqc @walter-erquinigo @clayborg since you
> commented on the other PR and might
https://github.com/ashgti updated
https://github.com/llvm/llvm-project/pull/132255
>From a696c1c3ce5cf0f652e0a016c5d5d422b2ae24d3 Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Thu, 20 Mar 2025 10:08:53 -0700
Subject: [PATCH 1/3] [lldb-dap] Adding a DAPError for showing users error
message
@@ -66,6 +75,40 @@ struct LLDBBaseTelemetryInfo : public
llvm::telemetry::TelemetryInfo {
void serialize(llvm::telemetry::Serializer &serializer) const override;
};
+/// Describes an exit status.
+struct ExitDescription {
+ int exit_code;
+ std::string description;
+};
+
felipepiovezan wrote:
Based on the 2013 commit that added those, I don't think there is a clean way
of testing this.
That said, since these methods simply forward to the underlying register
context, I think it's ok to rely on the lack of regression from the OS plugin
tests
https://github.com/
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: John Harrison (ashgti)
Changes
These tests are currently filtered on macOS if your on an M1 (or newer) device.
These tests do work on macOS, for me at least on M1 Max with macOS 15.3.2 and
Xcode 16.2.
Enabling them again, but if we have C
rocallahan wrote:
I suppose we need to add documentation for this but I'm not sure where...
https://github.com/llvm/llvm-project/pull/132783
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-
https://github.com/oontvoo updated
https://github.com/llvm/llvm-project/pull/132043
>From 9f0a47af2b7fdb90e4fa4cc7f8f97c840af1d2bc Mon Sep 17 00:00:00 2001
From: Vy Nguyen
Date: Wed, 19 Mar 2025 10:44:12 -0400
Subject: [PATCH 1/4] Reapply "[LLDB][Telemetry]Define TargetInfo for
collecting data
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Pavel Labath (labath)
Changes
This reverts commit 094904303d50e0ab14bc5f2586a602f79af95953, reapplying
d7afafdbc464e65c56a0a1d77bad426aa7538306 (#133247).
The failure ought to be fixed by
0509932bb6a291ba11253f30c465ab3ad164ae08.
---
Pat
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Dave Lee (kastiglione)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/131890.diff
1 Files Affected:
- (modified)
lldb/test/API/functionalities/breakpoint/breakpoint_locations/TestBreakpointLocations.py
(+2-2)
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/source/Plugins/Process/Utility/LinuxSignals.cpp
@@ -0,0 +1,130 @@
+import * as child_process from "node:child_process";
+import * as vscode from "vscode";
+
+function areArraysEqual(lhs: T[], rhs: T[]): boolean {
+ if (lhs.length !== rhs.length) {
+return false;
+ }
+ for (let i = 0; i < lhs.length; i++) {
+if (lhs[i
@@ -965,6 +965,22 @@ SBTarget SBDebugger::GetDummyTarget() {
return sb_target;
}
+void SBDebugger::DispatchClientTelemetry(const lldb::SBStructuredData &entry) {
+ LLDB_INSTRUMENT_VA(this);
+ // Disable client-telemetry for SWIG.
+ // This prevent arbitrary python client
@@ -0,0 +1,118 @@
+//===-- GoToRequestHandler.cpp --===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Apache-2.
https://github.com/JDevlieghere created
https://github.com/llvm/llvm-project/pull/133791
This makes the DAP test server resilient against broken pipes. I'm not sure
what is causing the broken pipe, but IIRC this isn't the first time we've seen
an issues related to that. I worry about swooping
https://github.com/ashgti approved this pull request.
Looks great!
https://github.com/llvm/llvm-project/pull/134030
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/ZhongUncle closed
https://github.com/llvm/llvm-project/pull/132360
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,283 @@
+//===-- DILParser.cpp
-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
https://github.com/labath created
https://github.com/llvm/llvm-project/pull/132395
The check is not correct for discontinuous functions, as one of the blocks
could very well begin before the function entry point. To catch dead-stripped
ranges, I check whether the functions is after the first k
ZhongUncle wrote:
I am not familiar with PR, so accidentally closed this PR. I create a new one
#132510
https://github.com/llvm/llvm-project/pull/132360
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/l
oontvoo wrote:
> @labath Hi, friendly ping? thanks
Sorry - ignore this ping, i put the comment on the wrong patch. meant to ping
on https://github.com/llvm/llvm-project/pull/129728
https://github.com/llvm/llvm-project/pull/132043
___
lldb-commits mai
https://github.com/ashgti edited
https://github.com/llvm/llvm-project/pull/130169
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -394,6 +394,13 @@ class TestGetTargetBreakpointsRequestHandler : public
LegacyRequestHandler {
void operator()(const llvm::json::Object &request) const override;
};
+class WriteMemoryRequestHandler : public LegacyRequestHandler {
vogelsgesang wrote:
I w
https://github.com/jimingham commented:
LGTM
https://github.com/llvm/llvm-project/pull/134204
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/134097
>From 151ad919ab6f2d87991511b293f4a9797210f82f Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 2 Apr 2025 15:48:25 +0100
Subject: [PATCH 1/4] [lldb][Target] RunThreadPlan to save/restore the
Execution
@@ -52,14 +37,33 @@ struct SourceBreakpoint : public Breakpoint {
static bool BreakpointHitCallback(void *baton, lldb::SBProcess &process,
lldb::SBThread &thread,
lldb::SBBreakpointLocation &location);
-}
https://github.com/dmpots created
https://github.com/llvm/llvm-project/pull/133826
The tests for the
[intel-pt](https://github.com/llvm/llvm-project/blob/348374028970c956f2e49ab7553b495d7408ccd9/lldb/docs/use/intel_pt.rst)
trace plugin were failing for multiple reasons.
On machines where traci
@@ -7,6 +7,9 @@
# CHECK: Stripped: false
# CHECK: Type: executable
# CHECK: Strata: unknown
+# CHECK: Name: .text
+# CHECK-NEXT: code
+# CHECK-NEXT: r-x
labath wrote:
The test is pretty weak. It should be very simple to add one of each kind of
sections that y
@@ -118,6 +118,19 @@ class StopInfo : public
std::enable_shared_from_this {
StructuredData::ObjectSP GetExtendedInfo() { return m_extended_info; }
+ /// Returns true if this is a stop reason that should be shown to a user when
+ /// stopping.
jimingham w
@@ -52,14 +37,33 @@ struct SourceBreakpoint : public Breakpoint {
static bool BreakpointHitCallback(void *baton, lldb::SBProcess &process,
lldb::SBThread &thread,
lldb::SBBreakpointLocation &location);
--
https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/133506
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dmpots created
https://github.com/llvm/llvm-project/pull/133794
This commit adds support for enabling and disabling plugins by name. The
changes are made generically in the `PluginInstances` class, but currently we
only expose the ability to SystemRuntime plugins. Other plug
Michael137 wrote:
Seems to be something else though?
```
An exception happened when receiving the response from the gdb server. Closing
the client...
An exception happened when receiving the response from the gdb server. Closing
the client...
An exception happened when receiving the response fr
Author: John Harrison
Date: 2025-03-31T15:51:07-07:00
New Revision: 4492632432190ed8ab3bc39ff8ee5ba9a89256cf
URL:
https://github.com/llvm/llvm-project/commit/4492632432190ed8ab3bc39ff8ee5ba9a89256cf
DIFF:
https://github.com/llvm/llvm-project/commit/4492632432190ed8ab3bc39ff8ee5ba9a89256cf.diff
https://github.com/adrian-prantl approved this pull request.
Will be great when debugging LLDB itself!
https://github.com/llvm/llvm-project/pull/133211
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/lis
Author: Igor Kudrin
Date: 2025-03-19T10:51:27-07:00
New Revision: 825460a7728662d0062405e690485b7a1b689484
URL:
https://github.com/llvm/llvm-project/commit/825460a7728662d0062405e690485b7a1b689484
DIFF:
https://github.com/llvm/llvm-project/commit/825460a7728662d0062405e690485b7a1b689484.diff
L
@@ -38,7 +39,7 @@ enum DWARFProducer {
eProducerOther
};
-class DWARFUnit : public UserID {
+class DWARFUnit : public UserID, public DWARFExpression::Delegate {
labath wrote:
```suggestion
class DWARFUnit : public DWARFExpression::Delegate, public UserID {
https://github.com/da-viper updated
https://github.com/llvm/llvm-project/pull/130503
>From 7bad765585b2ae96faf2d2558b099f4b965d2791 Mon Sep 17 00:00:00 2001
From: Ezike Ebuka
Date: Sun, 9 Mar 2025 12:46:54 +
Subject: [PATCH 01/23] [lldb-dap] implement jump to cursor.
---
lldb/cmake/module
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-x86_64-debian`
running on `lldb-x86_64-debian` while building `lldb` at step 6 "test".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/162/builds/18611
Here is the relevant piece of the build log
Author: Jonas Devlieghere
Date: 2025-04-02T08:50:28-07:00
New Revision: ee60f7c7a4e4e400918c83decb6cd498aff94012
URL:
https://github.com/llvm/llvm-project/commit/ee60f7c7a4e4e400918c83decb6cd498aff94012
DIFF:
https://github.com/llvm/llvm-project/commit/ee60f7c7a4e4e400918c83decb6cd498aff94012.d
@@ -463,6 +463,8 @@ void InitializeRequestHandler::operator()(
body.try_emplace("supportsDataBreakpoints", true);
// The debug adapter supports the `readMemory` request.
body.try_emplace("supportsReadMemoryRequest", true);
+ // The debug adapter supports the 'writeMemory
https://github.com/ashgti created
https://github.com/llvm/llvm-project/pull/133007
This adds new types and helpers to support the 'initialize' request with the
new typed RequestHandler. While working on this I found there were a few cases
where we incorrectly treated initialize arguments as ca
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Robert O'Callahan (rocallahan)
Changes
This introduces the options "-F/--forward" and "-R/--reverse" to `process
continue`.
These only work if you're running with a gdbserver backend that supports
reverse execution, such as rr. For testin
https://github.com/labath closed
https://github.com/llvm/llvm-project/pull/132008
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -146,6 +155,59 @@ struct DebuggerInfo : public LLDBBaseTelemetryInfo {
void serialize(llvm::telemetry::Serializer &serializer) const override;
};
+struct ExecModuleInfo : public LLDBBaseTelemetryInfo {
+ lldb::ModuleSP exec_mod;
+
+ /// The same as the executable-module
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Pavel Labath (labath)
Changes
The surrounding code doesn't use them anymore. This removes the internal usages.
This patch makes the Rows actual values. An alternative would be to make them
unique_ptrs. That would make vector resizes faster
https://github.com/labath updated
https://github.com/llvm/llvm-project/pull/127661
>From 22c489dbd334fb84b8d81deac8e7e6c5590fc6d9 Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Tue, 18 Feb 2025 16:14:30 +0100
Subject: [PATCH] [lldb] s/ValidRange/ValidRanges in UnwindPlan
To be able to descr
@@ -0,0 +1,32 @@
+// RUN: rm -rf %t && mkdir -p %t
+// RUN: clang-doc --format=md --doxygen --output=%t --executor=standalone %s
+// RUN: clang-doc --format=html --doxygen --output=%t --executor=standalone %s
+// RUN: FileCheck %s < %t/GlobalNamespace/MyClass.md
--check-prefix=MD
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/133249
>From 0875195a7ed39c21e9b639bf66d56b48e9869e51 Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Tue, 11 Mar 2025 08:57:13 +
Subject: [PATCH 1/4] [llvm][ItaniumDemangle] Add function name location
tracki
@@ -777,28 +798,134 @@ llvm::Error DAP::Disconnect(bool terminateDebuggee) {
return ToError(error);
}
+template
+static std::optional getArgumentsIfRequest(const protocol::Message &pm,
+ llvm::StringLiteral command) {
+ auto *co
ashgti wrote:
I did that while I was trying to figure out how to have `cancel` request
support. I was trying to close the FD to stop the reader thread, but that
actually doesn't interrupt in-progress `read` calls. I should have reverted
that when I did some of the `Transport` refactors. In my
JDevlieghere wrote:
This doesn't seem to be enough. When I added this, the SIGHUP disappeared for a
bunch of runs, but now I'm seeing it again, with this patch applied.
https://github.com/llvm/llvm-project/pull/133791
___
lldb-commits mailing list
ll
@@ -220,6 +220,8 @@ Changes to LLDB
information about the current state of the debugger at the bottom of the
terminal. This is on by default and can be configured using the
`show-statusline` and `statusline-format` settings.
+* LLDB now supports `process continue --revers
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-aarch64-ubuntu`
running on `linaro-lldb-aarch64-ubuntu` while building `lldb` at step 6 "test".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/59/builds/15220
Here is the relevant piece of the b
@@ -0,0 +1,273 @@
+//===-- DILParser.cpp
-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
https://github.com/JDevlieghere updated
https://github.com/llvm/llvm-project/pull/133506
>From 497d45360ad50ae909d946b4a34b55346c56ff69 Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere
Date: Fri, 28 Mar 2025 11:55:23 -0700
Subject: [PATCH 1/2] [lldb] Create a default rate limit constant in Prog
https://github.com/dmpots closed
https://github.com/llvm/llvm-project/pull/134173
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/royitaqi closed
https://github.com/llvm/llvm-project/pull/130912
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/132119
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
ktraunmueller wrote:
Just out of curiosity: I was also surprised by the precondition, which looks
unnecessary and, more importantly, very unexpected, to me.
How would a caller know (from looking at the API) that passing a non-empty
string would be fatal?
If there's a preconditions in the co
@@ -0,0 +1,100 @@
+## This test checks that lldb handles (corrupt?) debug info which has
improperly
+## nested blocks. The behavior here is not prescriptive. We only want to check
+## that we do something "reasonable".
+
+
+# RUN: llvm-mc -triple=x86_64-pc-linux -filetype=obj %s
https://github.com/oontvoo updated
https://github.com/llvm/llvm-project/pull/129728
>From 21103adacdf9c08cee4065f8a6b90ff812fefbb3 Mon Sep 17 00:00:00 2001
From: Vy Nguyen
Date: Tue, 4 Mar 2025 11:01:46 -0500
Subject: [PATCH 01/10] [LLDB][Telemetry] Collect telemetry from client when
allowed.
labath wrote:
@JDevlieghere, @jasonmolenda any chance I could get a review on this patch? Or
ask me questions -- I can explain where I'm trying to go with this.
As much as I like refactoring around this code, I do actually need to make
progress on adding the functionality. :)
https://github.c
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
351bcd9fe229121fac58e051f9a83dce2d3066ae...9a6d64373f45921c5b23460b12544869355ddd15
lldb/
https://github.com/JDevlieghere created
https://github.com/llvm/llvm-project/pull/133780
Convert Breakpoint & Watchpoints structs to classes to provide proper access
control. This is in preparation for adopting SBMutex to protect the underlying
SBBreakpoint and SBWatchpoint.
>From 2f22b24840e
https://github.com/ashgti updated
https://github.com/llvm/llvm-project/pull/130104
>From 2c51a8bdb27764a358e76e554d693a4af57074fc Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Thu, 6 Mar 2025 14:13:58 +0100
Subject: [PATCH] [lldb-dap] Adding support for well typed events.
This adds a mech
llvmbot wrote:
@llvm/pr-subscribers-clang-tools-extra
@llvm/pr-subscribers-clang
Author: Matheus Izvekov (mizvekov)
Changes
Original PR: #130537
Reland after updating lldb too.
This changes the MemberPointerType representation to use a NestedNameSpecifier
instead of a Type to represent t
https://github.com/dmpots updated
https://github.com/llvm/llvm-project/pull/132884
>From 6edc108199044d30eed396145aab463db40d6351 Mon Sep 17 00:00:00 2001
From: David Peixotto
Date: Thu, 13 Mar 2025 16:13:45 -0700
Subject: [PATCH 1/2] Remove raw access to PluginInstances vector
This commit mod
https://github.com/Jlalond approved this pull request.
https://github.com/llvm/llvm-project/pull/132255
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
kastiglione wrote:
@luporl https://github.com/llvm/llvm-project/pull/131890
https://github.com/llvm/llvm-project/pull/131475
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Michael137 wrote:
> LGTM. Even the variable name made it clear this wasn't being set correctly.
> We just usually do evaluate expressions in the selected frame context. This
> should cause a failure in the current code if you call
> SBThread.SetSelectedFrame for frame A and then get the SBFram
https://github.com/AlexK0 updated
https://github.com/llvm/llvm-project/pull/131600
>From 2186582c6113033a7adf2c3ac7fb1a6fcde5726c Mon Sep 17 00:00:00 2001
From: Aleksandr Korepanov
Date: Mon, 17 Mar 2025 11:03:57 +0100
Subject: [PATCH 1/2] [LLDB][tests] Transfer APPDATA env for running tests
O
llvmbot wrote:
/pull-request llvm/llvm-project#134072
https://github.com/llvm/llvm-project/pull/131519
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dmpots closed
https://github.com/llvm/llvm-project/pull/131951
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: John Harrison
Date: 2025-04-03T09:45:00-07:00
New Revision: bc6cd825ecea94f015c590c877a1401d3a4a46b8
URL:
https://github.com/llvm/llvm-project/commit/bc6cd825ecea94f015c590c877a1401d3a4a46b8
DIFF:
https://github.com/llvm/llvm-project/commit/bc6cd825ecea94f015c590c877a1401d3a4a46b8.diff
https://github.com/JDevlieghere edited
https://github.com/llvm/llvm-project/pull/133740
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/labath approved this pull request.
https://github.com/llvm/llvm-project/pull/132718
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Jonas Devlieghere
Date: 2025-03-31T08:19:41-07:00
New Revision: 50949ebf523cc09cc911a12691fb79b6ac97102a
URL:
https://github.com/llvm/llvm-project/commit/50949ebf523cc09cc911a12691fb79b6ac97102a
DIFF:
https://github.com/llvm/llvm-project/commit/50949ebf523cc09cc911a12691fb79b6ac97102a.d
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Jonas Devlieghere (JDevlieghere)
Changes
This moves two functions from Platform to Host:
1. GetCurrentXcodeToolchainDirectory
2. GetCurrentCommandLineToolsDirectory.
These two functions caused a layering violation in the Swift fork, wh
Author: Jonas Devlieghere
Date: 2025-03-31T23:53:35-07:00
New Revision: aa889ed129ff26d9341c50a9eaba4db728ca6212
URL:
https://github.com/llvm/llvm-project/commit/aa889ed129ff26d9341c50a9eaba4db728ca6212
DIFF:
https://github.com/llvm/llvm-project/commit/aa889ed129ff26d9341c50a9eaba4db728ca6212.d
labath wrote:
> LGTM. I got kind of excited by the value semantics, but I don't know how many
> copies we're talking about and this is an established way to guarantee
> pointer stability.
Yeah, this definitely feels less satisfying. It also feels a bit
path-dependent, as I don't think we'd fr
https://github.com/ashgti updated
https://github.com/llvm/llvm-project/pull/133624
>From 3240fe49515e5f59c5b9ff9c02423b77504d8a43 Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Fri, 28 Mar 2025 14:02:53 -0700
Subject: [PATCH 1/2] [lldb-dap] Refactoring lldb-dap 'launch' request to use
type
Author: John Harrison
Date: 2025-03-28T09:13:10-07:00
New Revision: 6526cda5d865d55b1db5aa0faffb29448e5c6a23
URL:
https://github.com/llvm/llvm-project/commit/6526cda5d865d55b1db5aa0faffb29448e5c6a23
DIFF:
https://github.com/llvm/llvm-project/commit/6526cda5d865d55b1db5aa0faffb29448e5c6a23.diff
labath wrote:
Thanks for reverting this while I was gone. It looks like there's still some
pointer persistence. I'll take a look at that a bit later...
https://github.com/llvm/llvm-project/pull/132370
___
lldb-commits mailing list
lldb-commits@lists.l
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Jordan Rupprecht (rupprecht)
Changes
This reverts commit d7cea2b18717f0cc31b7da4a03f772d89ee201db. It causes crashes
in API tests.
---
Full diff: https://github.com/llvm/llvm-project/pull/133299.diff
2 Files Affected:
- (modified) lldb/
cmtice wrote:
> > Okay, at this I don't think I have any more comments about functionality.
> > The remaining comments are either stylistic (which should be
> > self-explanatory) or about error handling (which I'm going to write about
> > here).
> > For the error handling, I missed the fact th
https://github.com/Jlalond approved this pull request.
Much improved! I should've noticed this in my first patch but great fix for the
flakiness
https://github.com/llvm/llvm-project/pull/134157
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
@@ -0,0 +1,258 @@
+//===-- DILParser.cpp
-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
@@ -190,8 +190,83 @@ void ObjectFileXCOFF::ParseSymtab(Symtab &lldb_symtab) {}
bool ObjectFileXCOFF::IsStripped() { return false; }
-void ObjectFileXCOFF::CreateSections(SectionList &unified_section_list) {}
-
+void ObjectFileXCOFF::CreateSections(SectionList &unified_section
@@ -3,7 +3,9 @@
(* This is currently a subset of the final DIL Language, matching the current
DIL implementation. *)
-expression = primary_expression ;
+expression = unary_expression ;
+
+unary_expression = unary_operator primary_expression ;
cmtice wrote:
https://github.com/slydiman updated
https://github.com/llvm/llvm-project/pull/132274
>From 40d69ed7386c3f8169b324bd3b7591a46e34ff4d Mon Sep 17 00:00:00 2001
From: Dmitry Vasilyev
Date: Thu, 20 Mar 2025 21:50:51 +0400
Subject: [PATCH] [LLDB] Refactored CPlusPlusLanguage::MethodName to break
lld
https://github.com/JDevlieghere created
https://github.com/llvm/llvm-project/pull/134048
While trying to make progress on #133782, I noticed that TestDAP_Progress was
taking 90 seconds to complete. This patch brings that down to 10 seocnds by
making the following changes:
1. Don't call `wait_
1 - 100 of 142 matches
Mail list logo
