slydiman wrote:
`lldb-shell::ProcessMachCoreArch.test` is flake.
But the following tests are broken by this commit (segmentation fault):
1. `lldb-api::TestMiniDump.py`:
```
2 _lldb.cpython-312-x86_64-linux-gnu.so 0x751c11a3cd14
3 libc.so.6 0x751c18845330
4
DhruvSrivastavaX wrote:
Sure, Thanks.
I have modified my test case for this one.
https://github.com/llvm/llvm-project/pull/131304
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/jasonmolenda updated
https://github.com/llvm/llvm-project/pull/134184
>From 7cc45f1a300b1b0f2cbb529f11a0f9e56c41ffea Mon Sep 17 00:00:00 2001
From: Jason Molenda
Date: Wed, 2 Apr 2025 18:05:29 -0700
Subject: [PATCH 1/2] [lldb][debugserver] Save and restore the SVE/SME registe
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Jonas Devlieghere (JDevlieghere)
Changes
The examples on this page were using the Python 2-style print. I ran the
updated code examples under Python 3 to confirm they are still up-to-date.
---
Full diff: https://github.com/llvm/llvm-projec
Author: Vladislav Dzhidzhoev
Date: 2025-04-03T11:33:11+02:00
New Revision: 094904303d50e0ab14bc5f2586a602f79af95953
URL:
https://github.com/llvm/llvm-project/commit/094904303d50e0ab14bc5f2586a602f79af95953
DIFF:
https://github.com/llvm/llvm-project/commit/094904303d50e0ab14bc5f2586a602f79af9595
https://github.com/kusmour updated
https://github.com/llvm/llvm-project/pull/134339
>From 18e4af1c5798b620e96a4447cb8cdab272775909 Mon Sep 17 00:00:00 2001
From: Wanyi Ye
Date: Thu, 3 Apr 2025 21:02:04 -0400
Subject: [PATCH] [lldb-dap] Always stop on enrty for attaching
Recently upon debugging
https://github.com/kusmour edited
https://github.com/llvm/llvm-project/pull/134339
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev approved this pull request.
I wasn't able to reproduce the problem locally either, but I've got the same
failing tests with the same stack traces by setting
```
const UnwindPlan::Row *active_row = (const UnwindPlan::Row *) 0x1;
```
I think it should work.
https://g
https://github.com/ashgti closed
https://github.com/llvm/llvm-project/pull/133960
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
z2oh wrote:
Cherrypick is up: https://github.com/swiftlang/llvm-project/pull/10415. Thanks
@JDevlieghere!
@ktraunmueller, ah I should've checked for an issue first, you had already done
the investigation! I'm in favor of the documentation change you propose. I'd
_also_ be in favor of just rem
yuvald-sweet-security wrote:
Should be good now
https://github.com/llvm/llvm-project/pull/131609
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/jimingham approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/134203
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
jayfoad wrote:
> Please try not to create big PRs that are crossing subproject boundaries,
> you'll have a hard time finding a reviewer will to sign off of a patch that
> Rouches other parts of the project. 10 small/trivial PRs are less work for
> the reviewers than one big one.
Fair enough.
https://github.com/ashgti updated
https://github.com/llvm/llvm-project/pull/130169
>From c183231db80d6c97bdd5e9bd0b21d041189146e8 Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Tue, 18 Mar 2025 14:05:38 -0700
Subject: [PATCH 01/15] [lldb-dap] Adding support for cancelling a request.
Adding
https://github.com/JDevlieghere closed
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/labath approved this pull request.
Okay, I think we're ready now. Thank you for your patience. Just a couple of
last minute cosmetic tweaks here. I've added a some include statements to make
the headers more self contained, but I'm sure I've missed some.
https://github.com/l
@@ -6176,6 +6180,10 @@ struct ManglingParser :
AbstractManglingParser, Alloc> {
Alloc>::AbstractManglingParser;
};
+inline void OutputBuffer::printLeft(const Node &N) { N.printLeft(*this); }
zygoloid wrote:
Thanks, yes. I agree
https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/134203
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
z2oh wrote:
I captured one above:
```
# Child-SP RetAddr Call Site
00 00d2`44b8ea48 7ff8`beefc12e ntdll!NtTerminateProcess+0x14
01 00d2`44b8ea50 7ff8`bcf518ab ntdll!RtlExitUserProcess+0x11e
02 00d2`44b8ea80 7ff8`bc0e0143
KERNEL32!ExitPr
@@ -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:
@@ -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:
compnerd wrote:
I think that a fully symbolicated stack trace would be very helpful. It might
explain the reason for the precondition.
https://github.com/llvm/llvm-project/pull/134150
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://l
https://github.com/slydiman updated
https://github.com/llvm/llvm-project/pull/132274
>From ba94c683a3d652a14a13313653bc70d5430e7b83 Mon Sep 17 00:00:00 2001
From: Dmitry Vasilyev
Date: Thu, 20 Mar 2025 21:50:51 +0400
Subject: [PATCH] [LLDB] Refactor Module::LookupInfo constructor and move out
SuibianP wrote:
Pinging @ashgti and @walter-erquinigo for review before I forget again
https://github.com/llvm/llvm-project/pull/121269
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commi
Author: Jonas Devlieghere
Date: 2025-04-03T13:51:17-07:00
New Revision: 5f99e0d4b9ea071e29a9cba75619d26811ff76c2
URL:
https://github.com/llvm/llvm-project/commit/5f99e0d4b9ea071e29a9cba75619d26811ff76c2
DIFF:
https://github.com/llvm/llvm-project/commit/5f99e0d4b9ea071e29a9cba75619d26811ff76c2.d
Author: Jonas Devlieghere
Date: 2025-04-03T09:08:23-07:00
New Revision: bec5cfd970c5882c54a9e8d9f3da430dc39d0dd0
URL:
https://github.com/llvm/llvm-project/commit/bec5cfd970c5882c54a9e8d9f3da430dc39d0dd0
DIFF:
https://github.com/llvm/llvm-project/commit/bec5cfd970c5882c54a9e8d9f3da430dc39d0dd0.d
Author: Jason Molenda
Date: 2025-04-03T15:48:54-07:00
New Revision: f1c6612202d88cbde224387621327a31609f2177
URL:
https://github.com/llvm/llvm-project/commit/f1c6612202d88cbde224387621327a31609f2177
DIFF:
https://github.com/llvm/llvm-project/commit/f1c6612202d88cbde224387621327a31609f2177.diff
https://github.com/jasonmolenda edited
https://github.com/llvm/llvm-project/pull/134314
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
ktraunmueller wrote:
@compnerd weighed in that assertions [are always there for a
reason](https://github.com/swiftlang/llvm-project/issues/10269#issuecomment-2772945096),
and I would generally agree on that 100%, but this precondition just doesn't
seem to make sense, so I would agree that remo
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Wanyi (kusmour)
Changes
Recently upon debugging a program with thousands of threads in VS Code,
lldb-dap would hang at a `threads` request sent right after receiving the
`configurationDone` response. Soon after it will end the debug sessio
https://github.com/kusmour created
https://github.com/llvm/llvm-project/pull/134339
Recently upon debugging a program with thousands of threads in VS Code,
lldb-dap would hang at a `threads` request sent right after receiving the
`configurationDone` response. Soon after it will end the debug s
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/tools/lldb-dap/attach/multithreading.cp
dlav-sc wrote:
> It matches only one of many possible lr.[wd]/sc.[wd] sequences.
I was confused too when I saw this for the first time. I expected to see a
processing a sequence of integer instructions between lr and sc. This patch was
enough to fix my issue, so I decided to bring it here as i
clayborg wrote:
Just a quick comment here for this:
```
/// Get if the symbol file for this module is loaded.
bool IsDebugInfoLoaded() const;
```
This isn't clear what it is returning. What it seems like it should be
returning from the name is "are there debug symbols in this module. But wha
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/4] [lldb-dap] Refactoring lldb-dap 'launch' request to use
type
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/3] [lldb-dap] Refactoring lldb-dap 'launch' request to use
type
https://github.com/oontvoo created
https://github.com/llvm/llvm-project/pull/134296
Details: detailed_command_telemetry (bool) and command_id (int) could already
be freed when the dispatcher's dtor runs. So we should just copy them into the
lambda since they are cheap.
>From 96025fd1183f257c
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Vy Nguyen (oontvoo)
Changes
Details: detailed_command_telemetry (bool) and command_id (int) could already
be freed when the dispatcher's dtor runs. So we should just copy them into the
lambda since they are cheap.
---
Full diff: https://
https://github.com/yln created https://github.com/llvm/llvm-project/pull/134323
Add integration test for libsanitizers trace collection
(`SanitizersAllocationTraces=all`).
rdar://144244084
>From 8aa5e0e7f97df7627187bbd8ad4b3df51c798f4f Mon Sep 17 00:00:00 2001
From: Julian Lettner
Date: T
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Julian Lettner (yln)
Changes
Add integration test for libsanitizers trace collection
(`SanitizersAllocationTraces=all`).
rdar://144244084
---
Full diff: https://github.com/llvm/llvm-project/pull/134323.diff
3 Files Affected:
- (mod
https://github.com/slydiman updated
https://github.com/llvm/llvm-project/pull/132274
>From a4d62ca1dfaca8eb29ce7d2809c28137d22416b9 Mon Sep 17 00:00:00 2001
From: Dmitry Vasilyev
Date: Thu, 20 Mar 2025 21:50:51 +0400
Subject: [PATCH] [LLDB] Refactor Module::LookupInfo constructor and move out
https://github.com/youngd007 created
https://github.com/llvm/llvm-project/pull/134266
As the DAP JSON was recently modified to move the statistics from one key to
another, it was revealed there was no test for the initialized event that also
emits this information.
https://github.com/llvm/llvm
https://github.com/jasonmolenda updated
https://github.com/llvm/llvm-project/pull/134314
>From 780fc8f5081f97234749c70a139ad6034f48f3ae Mon Sep 17 00:00:00 2001
From: Jason Molenda
Date: Thu, 3 Apr 2025 15:38:23 -0700
Subject: [PATCH 1/2] [lldb][debugserver] Fix an off-by-one error in watchpoin
@@ -36,34 +42,61 @@ def setUp(self):
self.line_breakpoint = line_number("main.c", "// break line")
# Test line numbers: rdar://126237493
-def libsanitizer_tests(self):
-target = self.createTestTarget()
+# for libsanitizers and remove `skip_line_numb
@@ -15,17 +15,23 @@ class AsanTestCase(TestBase):
@expectedFailureNetBSD
@skipUnlessAddressSanitizer
def test(self):
-self.build(make_targets=["asan"])
+self.build(make_targets=["compiler_rt-asan"])
self.asan_tests()
wrotki
@@ -15,17 +15,23 @@ class AsanTestCase(TestBase):
@expectedFailureNetBSD
@skipUnlessAddressSanitizer
def test(self):
-self.build(make_targets=["asan"])
+self.build(make_targets=["compiler_rt-asan"])
self.asan_tests()
-@skipIf(oslist=no
https://github.com/Jlalond closed
https://github.com/llvm/llvm-project/pull/134341
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kusmour edited
https://github.com/llvm/llvm-project/pull/134339
___
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
Reverts llvm/llvm-project#134163
Reverting while @clayborg and I come up with a better API
---
Full diff: https://github.com/llvm/llvm-project/pull/134341.diff
2 Files Affected:
- (modified) lldb/include/
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Jonas Devlieghere (JDevlieghere)
Changes
The `lldbassert` macro in LLDB behaves like a regular `assert` when assertions
are enabled, and otherwise prints a pretty backtrace and prompts the user to
file a bug. By default, this is emitted as
https://github.com/JDevlieghere created
https://github.com/llvm/llvm-project/pull/134343
The `lldbassert` macro in LLDB behaves like a regular `assert` when assertions
are enabled, and otherwise prints a pretty backtrace and prompts the user to
file a bug. By default, this is emitted as a diag
Author: cmtice
Date: 2025-04-03T21:39:30-07:00
New Revision: 46e2c07fa28bd42da8f8ca52e93603297114afa2
URL:
https://github.com/llvm/llvm-project/commit/46e2c07fa28bd42da8f8ca52e93603297114afa2
DIFF:
https://github.com/llvm/llvm-project/commit/46e2c07fa28bd42da8f8ca52e93603297114afa2.diff
LOG: [
https://github.com/cmtice closed
https://github.com/llvm/llvm-project/pull/120971
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-arm-ubuntu` running
on `linaro-lldb-arm-ubuntu` while building `lldb` at step 6 "test".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/18/builds/13991
Here is the relevant piece of the build log
Author: Pavel Labath
Date: 2025-04-03T11:59:02+02:00
New Revision: 662d385c7b07fc6aba51e73a09c254f551ab93ab
URL:
https://github.com/llvm/llvm-project/commit/662d385c7b07fc6aba51e73a09c254f551ab93ab
DIFF:
https://github.com/llvm/llvm-project/commit/662d385c7b07fc6aba51e73a09c254f551ab93ab.diff
https://github.com/labath closed
https://github.com/llvm/llvm-project/pull/134078
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Michael137 closed
https://github.com/llvm/llvm-project/pull/134097
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/yuvald-sweet-security updated
https://github.com/llvm/llvm-project/pull/131609
>From 6f2d070facaced221295a5b0c48ccb3a41a5048d Mon Sep 17 00:00:00 2001
From: Yuval Deutscher
Date: Mon, 17 Mar 2025 14:37:26 +0200
Subject: [PATCH 1/2] [lldb] Use correct path for debugserver
---
https://github.com/yuvald-sweet-security updated
https://github.com/llvm/llvm-project/pull/131609
>From 6f2d070facaced221295a5b0c48ccb3a41a5048d Mon Sep 17 00:00:00 2001
From: Yuval Deutscher
Date: Mon, 17 Mar 2025 14:37:26 +0200
Subject: [PATCH 1/2] [lldb] Use correct path for debugserver
---
DavidSpickett wrote:
Given how fiddly this all is, I would duplicate the test (meaning, add another
test case to that file). Even if there is overlap, it's worth it for the added
clarity.
https://github.com/llvm/llvm-project/pull/131609
___
lldb-comm
yuvald-sweet-security wrote:
Whoops, I copied that test and didn't read what it does at the end
https://github.com/llvm/llvm-project/pull/131609
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/l
https://github.com/yuvald-sweet-security updated
https://github.com/llvm/llvm-project/pull/131609
>From 6f2d070facaced221295a5b0c48ccb3a41a5048d Mon Sep 17 00:00:00 2001
From: Yuval Deutscher
Date: Mon, 17 Mar 2025 14:37:26 +0200
Subject: [PATCH 1/2] [lldb] Use correct path for debugserver
---
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/3] [llvm][ItaniumDemangle] Add function name location
tracki
Author: Michael Buch
Date: 2025-04-03T12:21:46+01:00
New Revision: 739fe980802e17e49ab9cc2e4c18a48c88e15ef5
URL:
https://github.com/llvm/llvm-project/commit/739fe980802e17e49ab9cc2e4c18a48c88e15ef5
DIFF:
https://github.com/llvm/llvm-project/commit/739fe980802e17e49ab9cc2e4c18a48c88e15ef5.diff
@@ -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
@@ -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
Author: Pavel Labath
Date: 2025-04-03T15:15:09+02:00
New Revision: 0509932bb6a291ba11253f30c465ab3ad164ae08
URL:
https://github.com/llvm/llvm-project/commit/0509932bb6a291ba11253f30c465ab3ad164ae08
DIFF:
https://github.com/llvm/llvm-project/commit/0509932bb6a291ba11253f30c465ab3ad164ae08.diff
labath wrote:
(I wasn't able to reproduce this on my end, but I'm fairly certain that
0509932bb6a291ba11253f30c465ab3ad164ae08 fixes at least one of the crashes)
https://github.com/llvm/llvm-project/pull/134246
___
lldb-commits mailing list
lldb-commi
yuvald-sweet-security wrote:
Wrote a test and it seems to pass CI, what do you say?
https://github.com/llvm/llvm-project/pull/131609
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/ashgti updated
https://github.com/llvm/llvm-project/pull/133960
>From 11ff51134e0632d800806e2319ce14bbb914ec2f Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Tue, 1 Apr 2025 11:27:31 -0700
Subject: [PATCH 1/2] [lldb-dap] Creating a common configuration structure for
laun
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: John Harrison (ashgti)
Changes
This moves all the common settings of the launch and attach operations into the
`lldb_dap::protocol::DAPConfiguration`. These common settings can be in both
`launch` and `attach` requests and allows us to iso
@@ -118,6 +118,81 @@ bool fromJSON(const llvm::json::Value &,
InitializeRequestArguments &,
/// Response to `initialize` request. The capabilities of this debug adapter.
using InitializeResponseBody = std::optional;
+/// DAP Launch and Attach common configurations.
+struct DA
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/2] [llvm][ItaniumDemangle] Add function name location
tracki
@@ -6176,6 +6180,10 @@ struct ManglingParser :
AbstractManglingParser, Alloc> {
Alloc>::AbstractManglingParser;
};
+inline void OutputBuffer::printLeft(const Node &N) { N.printLeft(*this); }
Michael137 wrote:
@zygoloid is this
https://github.com/DhruvSrivastavaX updated
https://github.com/llvm/llvm-project/pull/131304
>From 106e137fea7d4b420ce3d97a8df16c3a91400997 Mon Sep 17 00:00:00 2001
From: Dhruv-Srivastava
Date: Fri, 14 Mar 2025 02:51:21 -0500
Subject: [PATCH 1/3] Support for XCOFF Sections
---
.../ObjectFile/
@@ -0,0 +1,61 @@
+//===-- DILEval.h ---*- C++
-*-===//
+//
+// 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: Apa
@@ -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
@@ -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
@@ -0,0 +1,95 @@
+//===-- DILAST.h *- C++
-*-===//
+//
+// 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: Apa
https://github.com/labath edited
https://github.com/llvm/llvm-project/pull/120971
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,236 @@
+//===-- DILEval.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
@@ -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
https://github.com/felipepiovezan updated
https://github.com/llvm/llvm-project/pull/134160
>From 48150d4bb0daf57b708f4fa86285f028eeff0da6 Mon Sep 17 00:00:00 2001
From: Felipe de Azevedo Piovezan
Date: Wed, 2 Apr 2025 09:28:56 -0700
Subject: [PATCH 1/3] [lldb][NFC] Move ShouldShow/ShouldSelect
https://github.com/JDevlieghere closed
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
Author: Felipe de Azevedo Piovezan
Date: 2025-04-03T07:41:29-07:00
New Revision: c14b6e90bd140c2290258fa9dbe0fc1ad8939111
URL:
https://github.com/llvm/llvm-project/commit/c14b6e90bd140c2290258fa9dbe0fc1ad8939111
DIFF:
https://github.com/llvm/llvm-project/commit/c14b6e90bd140c2290258fa9dbe0fc1ad
https://github.com/felipepiovezan closed
https://github.com/llvm/llvm-project/pull/134160
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
86 matches
Mail list logo
