https://github.com/JDevlieghere updated
https://github.com/llvm/llvm-project/pull/143628
>From 4b0e386016e3ee0d74a673e4f857b5537309614f Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere
Date: Wed, 4 Jun 2025 23:56:57 -0700
Subject: [PATCH] [lldb] Add MCP support to LLDB (PoC)
---
lldb/include/
https://github.com/ChuanqiXu9 approved this pull request.
Thanks. I feel good with it.
https://github.com/llvm/llvm-project/pull/141889
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commi
https://github.com/royitaqi edited
https://github.com/llvm/llvm-project/pull/143633
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -933,6 +933,9 @@ static Triple::ObjectFormatType getDefaultFormat(const
Triple &T) {
case Triple::Win32:
case Triple::UEFI:
return Triple::COFF;
+case Triple::UnknownOS:
+ return T.getVendor() == Triple::Apple ? Triple::MachO : Triple::ELF;
+ //
https://github.com/royitaqi edited
https://github.com/llvm/llvm-project/pull/143633
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/royitaqi edited
https://github.com/llvm/llvm-project/pull/143633
___
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: None (royitaqi)
Changes
**Context**: See previous attempt #142704
**TL;DR**: Some mach-o files (including some of those in lldb tests) are
mistakenly reported as `ELF` (as in their `Triple`) by `ObjectFileMachO`. The
reason is that those
https://github.com/royitaqi created
https://github.com/llvm/llvm-project/pull/143633
**Context**: See previous attempt #142704
**TL;DR**: Some mach-o files (including some of those in lldb tests) are
mistakenly reported as `ELF` (as in their `Triple`) by `ObjectFileMachO`. The
reason is that
https://github.com/JDevlieghere edited
https://github.com/llvm/llvm-project/pull/143628
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/JDevlieghere created
https://github.com/llvm/llvm-project/pull/143628
None
>From 621d239bf5221433a2fb0ebf6858a814f38b9241 Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere
Date: Wed, 4 Jun 2025 23:56:57 -0700
Subject: [PATCH] [lldb] Add MCP support to LLDB (PoC)
---
lldb/in
Author: Jonas Devlieghere
Date: 2025-06-10T15:36:55-07:00
New Revision: c7063380205d8776e281f7a6603119aa8ea28c12
URL:
https://github.com/llvm/llvm-project/commit/c7063380205d8776e281f7a6603119aa8ea28c12
DIFF:
https://github.com/llvm/llvm-project/commit/c7063380205d8776e281f7a6603119aa8ea28c12.d
jasonmolenda wrote:
I thought we augmented the target.xml from the remote gdb stub via
`ABI::AugmentRegisterInfo` -- adding eh_frame/dwarf register numbers that were
not supplied by the stub, for instance -- but looking at AArch64 & x86, it
looks like it's just adding the slice registers like
https://github.com/felipepiovezan updated
https://github.com/llvm/llvm-project/pull/143572
>From 9821fd7c4530819f131271f4325123a400ecded4 Mon Sep 17 00:00:00 2001
From: Felipe de Azevedo Piovezan
Date: Tue, 10 Jun 2025 10:26:52 -0700
Subject: [PATCH 1/3] [lldb][nfc] Factor out code checking if
@@ -321,6 +302,27 @@ bool Variable::IsInScope(StackFrame *frame) {
return false;
}
+bool Variable::IsInScope(Block &block, Address addr) {
felipepiovezan wrote:
That's an interesting, given the current usage it makes sense to switch this to
const reference
jasonmolenda wrote:
Thanks for help, I didn't realize I regressed this with my NFC reorg.
https://github.com/llvm/llvm-project/pull/143499
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-co
@@ -321,6 +302,27 @@ bool Variable::IsInScope(StackFrame *frame) {
return false;
}
+bool Variable::IsInScope(Block &block, Address addr) {
JDevlieghere wrote:
A quick grep shows 223 instances of it being passed by const ref and the class
itself seems to be
vogelsgesang wrote:
@labath @adrian-prantl friendly ping 🙂
https://github.com/llvm/llvm-project/pull/141516
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/141516
>From 82aa5d13eb9cc73c7e45cb3f4a9e32cd5639 Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Fri, 23 May 2025 01:20:46 +
Subject: [PATCH] [lldb] Show coro_frame in `std::coroutine_handle` pre
@@ -321,6 +302,27 @@ bool Variable::IsInScope(StackFrame *frame) {
return false;
}
+bool Variable::IsInScope(Block &block, Address addr) {
felipepiovezan wrote:
Mmmm it is a weak pointer + integer. How cheap is it to copy a weak pointer?
https://github.com
@@ -321,6 +302,27 @@ bool Variable::IsInScope(StackFrame *frame) {
return false;
}
+bool Variable::IsInScope(Block &block, Address addr) {
felipepiovezan wrote:
>Like
>[std::shared_ptr](https://en.cppreference.com/w/cpp/memory/shared_ptr.html), a
>typical
@@ -321,6 +302,27 @@ bool Variable::IsInScope(StackFrame *frame) {
return false;
}
+bool Variable::IsInScope(Block &block, Address addr) {
felipepiovezan wrote:
That one is just a pointer + integer, my understanding is that it is supposed
to be passed by v
@@ -321,6 +302,27 @@ bool Variable::IsInScope(StackFrame *frame) {
return false;
}
+bool Variable::IsInScope(Block &block, Address addr) {
JDevlieghere wrote:
What about `Address`? :D
https://github.com/llvm/llvm-project/pull/143572
__
https://github.com/felipepiovezan updated
https://github.com/llvm/llvm-project/pull/143572
>From 9821fd7c4530819f131271f4325123a400ecded4 Mon Sep 17 00:00:00 2001
From: Felipe de Azevedo Piovezan
Date: Tue, 10 Jun 2025 10:26:52 -0700
Subject: [PATCH 1/2] [lldb][nfc] Factor out code checking if
@@ -321,6 +302,27 @@ bool Variable::IsInScope(StackFrame *frame) {
return false;
}
+bool Variable::IsInScope(Block &block, Address addr) {
felipepiovezan wrote:
Just an oopsie on my part!
https://github.com/llvm/llvm-project/pull/143572
___
vogelsgesang wrote:
@ChuanqiXu9 do you want to take another look? (given that this is a NFC for
Swift, and primarily changes C++ behavior)
Alternatively, is it fine by you if I ship this based on @Michael137's approval?
https://github.com/llvm/llvm-project/pull/141889
__
vogelsgesang wrote:
> The LLDB test failure seems expected. The demangled frame name changed
Good catch. I updated the LLDB test expectations just now
https://github.com/llvm/llvm-project/pull/141889
___
lldb-commits mailing list
lldb-commits@lists.ll
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/141889
>From 700c1c465ff7f29dc980356f36844a12d580 Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Tue, 27 May 2025 23:50:18 +
Subject: [PATCH 1/3] [debuginfo][coro] Fix linkage name for clones of
https://github.com/chelcassanova updated
https://github.com/llvm/llvm-project/pull/142051
>From 2d63dfe6e4f9671d3c22c319e01782aacee303e4 Mon Sep 17 00:00:00 2001
From: Chelsea Cassanova
Date: Wed, 28 May 2025 15:45:45 -0700
Subject: [PATCH] [lldb][headers] Create Python script to fix up framewo
Author: Jonas Devlieghere
Date: 2025-06-10T13:30:31-07:00
New Revision: a7f495f170864e6bddc4bb29ae7fae293a7136aa
URL:
https://github.com/llvm/llvm-project/commit/a7f495f170864e6bddc4bb29ae7fae293a7136aa
DIFF:
https://github.com/llvm/llvm-project/commit/a7f495f170864e6bddc4bb29ae7fae293a7136aa.d
https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/142244
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -321,6 +302,27 @@ bool Variable::IsInScope(StackFrame *frame) {
return false;
}
+bool Variable::IsInScope(Block &block, Address addr) {
JDevlieghere wrote:
Any reason to not pass this by const ref?
https://github.com/llvm/llvm-project/pull/143572
__
kazutakahirata wrote:
@labath I've landed 50313a5f556b9967e7d8eb53ee45f79f0fc5b2b8 to fix warnings
from this PR. Thanks!
https://github.com/llvm/llvm-project/pull/143499
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org
Author: Kazu Hirata
Date: 2025-06-10T11:27:30-07:00
New Revision: 50313a5f556b9967e7d8eb53ee45f79f0fc5b2b8
URL:
https://github.com/llvm/llvm-project/commit/50313a5f556b9967e7d8eb53ee45f79f0fc5b2b8
DIFF:
https://github.com/llvm/llvm-project/commit/50313a5f556b9967e7d8eb53ee45f79f0fc5b2b8.diff
L
Author: Pavel Labath
Date: 2025-06-10T19:50:33+02:00
New Revision: 74a012ed756f5280c71e281c0fd2dd50f83f38b7
URL:
https://github.com/llvm/llvm-project/commit/74a012ed756f5280c71e281c0fd2dd50f83f38b7
DIFF:
https://github.com/llvm/llvm-project/commit/74a012ed756f5280c71e281c0fd2dd50f83f38b7.diff
https://github.com/labath closed
https://github.com/llvm/llvm-project/pull/143499
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
labath wrote:
Thanks.
https://github.com/llvm/llvm-project/pull/143499
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/ashgti closed
https://github.com/llvm/llvm-project/pull/142831
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: John Harrison
Date: 2025-06-10T10:49:07-07:00
New Revision: 07a1d479cc4e2d529b04cecb2f97ff16f32ef197
URL:
https://github.com/llvm/llvm-project/commit/07a1d479cc4e2d529b04cecb2f97ff16f32ef197
DIFF:
https://github.com/llvm/llvm-project/commit/07a1d479cc4e2d529b04cecb2f97ff16f32ef197.diff
jimingham wrote:
It also seems architecturally wrong to try to guess and influence what
BreakpointResolvers do behind their backs. After all, the resolver might be
just some Python Code you know nothing about. How would you instrument that?
If I set a regular expression name breakpoint, wil
https://github.com/felipepiovezan created
https://github.com/llvm/llvm-project/pull/143572
This is useful for checking whether a variable is in scope inside a specific
block.
>From 9821fd7c4530819f131271f4325123a400ecded4 Mon Sep 17 00:00:00 2001
From: Felipe de Azevedo Piovezan
Date: Tue, 10
https://github.com/ashgti updated
https://github.com/llvm/llvm-project/pull/142831
>From 0824e3c626ad5e8c2ce37f2fdfcf0c2fa47b7b1d Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Wed, 4 Jun 2025 11:03:37 -0700
Subject: [PATCH 1/8] [lldb-dap] Creating a 'capabilities' event helper.
This adds
ashgti wrote:
I think more of the tests I see are using style 4, so I went with that for my
tests for consistency.
https://github.com/llvm/llvm-project/pull/142831
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bi
https://github.com/chelcassanova closed
https://github.com/llvm/llvm-project/pull/142871
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Chelsea Cassanova
Date: 2025-06-10T09:47:11-07:00
New Revision: eb76d8332e932dfda133fe95331e6910805a27c5
URL:
https://github.com/llvm/llvm-project/commit/eb76d8332e932dfda133fe95331e6910805a27c5
DIFF:
https://github.com/llvm/llvm-project/commit/eb76d8332e932dfda133fe95331e6910805a27c5.d
Author: satyajanga
Date: 2025-06-10T09:25:28-07:00
New Revision: 1cb906e8325d2b73054f2b4fa943b66377152f37
URL:
https://github.com/llvm/llvm-project/commit/1cb906e8325d2b73054f2b4fa943b66377152f37
DIFF:
https://github.com/llvm/llvm-project/commit/1cb906e8325d2b73054f2b4fa943b66377152f37.diff
LO
https://github.com/Jlalond closed
https://github.com/llvm/llvm-project/pull/142875
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/JDevlieghere approved this pull request.
https://github.com/llvm/llvm-project/pull/142831
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
JDevlieghere wrote:
> I would go with either style2 or style 4 because of the default
> initialisation needed in `fromJSON`
+1 on either 2 or 4.
https://github.com/llvm/llvm-project/pull/142831
___
lldb-commits mailing list
lldb-commits@lists.llvm.or
https://github.com/JDevlieghere approved this pull request.
https://github.com/llvm/llvm-project/pull/142871
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
beetrees wrote:
Ping @JDevlieghere: I think this is ready to merge.
https://github.com/llvm/llvm-project/pull/98369
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
labath wrote:
Sorry about the delay. I have very mixed feelings about this PR. I too found
the existing method of synchronization extremely clunky, so I definitely
wouldn't be sad to see it go. However, I also have some reservations about this
implementation:
- you say you're assuming a single
https://github.com/da-viper updated
https://github.com/llvm/llvm-project/pull/143126
>From 95c61d6a917060d7b3a2bc554575eb6a1086ed6e Mon Sep 17 00:00:00 2001
From: Ebuka Ezike
Date: Fri, 6 Jun 2025 13:15:41 +0100
Subject: [PATCH 1/6] [lldb] add plugin names to process save-core error
output.
-
https://github.com/labath created
https://github.com/llvm/llvm-project/pull/143499
This fixes a regression caused by #139817, where we would fail to unwind (using
eh_frame) when using debug stubs (like qemu) which do not provide eh_frame
register numbers.
Unwinding fails because the unwinder
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Pavel Labath (labath)
Changes
This fixes a regression caused by #139817, where we would fail to
unwind (using eh_frame) when using debug stubs (like qemu) which do not provide
eh_frame register numbers.
Unwinding fails because the unwinde
Author: Michael Buch
Date: 2025-06-10T10:58:16+01:00
New Revision: 95b5b6801ce4c08e1bc92616321cd4127e7c0957
URL:
https://github.com/llvm/llvm-project/commit/95b5b6801ce4c08e1bc92616321cd4127e7c0957
DIFF:
https://github.com/llvm/llvm-project/commit/95b5b6801ce4c08e1bc92616321cd4127e7c0957.diff
Author: Pavel Labath
Date: 2025-06-10T11:58:39+02:00
New Revision: 7e471c1fd0c4de4656cfaac39e247d207e987510
URL:
https://github.com/llvm/llvm-project/commit/7e471c1fd0c4de4656cfaac39e247d207e987510
DIFF:
https://github.com/llvm/llvm-project/commit/7e471c1fd0c4de4656cfaac39e247d207e987510.diff
https://github.com/labath closed
https://github.com/llvm/llvm-project/pull/142587
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/DavidSpickett closed
https://github.com/llvm/llvm-project/pull/143385
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: David Spickett
Date: 2025-06-10T09:59:16+01:00
New Revision: 6ec48b449fb60a766d4faf185613f1b4a8638bfa
URL:
https://github.com/llvm/llvm-project/commit/6ec48b449fb60a766d4faf185613f1b4a8638bfa
DIFF:
https://github.com/llvm/llvm-project/commit/6ec48b449fb60a766d4faf185613f1b4a8638bfa.diff
https://github.com/labath updated
https://github.com/llvm/llvm-project/pull/142587
>From e040dfb3270ca1101ec0c86d74dce26b2d10914a Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Tue, 3 Jun 2025 13:45:04 +0200
Subject: [PATCH] [lldb/cmake] Use ADDITIONAL_HEADER(_DIR)?S
Replace (questionable)
labath wrote:
The code is fine, but you should really add a test for it. You don't need to
wait for lldb-test to grow symtab support. You can write a test that does
something like:
```
# RUN: yaml2obj %s > %t
# RUN: %lldb %t -o "image dump symtab" -o exit | FileCheck %s
# CHECK: symtab contents
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/143177
>From 938bc84e55cff4a5e852f0ea093e95418e9b4374 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Fri, 6 Jun 2025 19:23:04 +0200
Subject: [PATCH] [LLDB] Add type summaries for MSVC STL strings
---
.../lldb/DataForma
https://github.com/da-viper updated
https://github.com/llvm/llvm-project/pull/143126
>From 95c61d6a917060d7b3a2bc554575eb6a1086ed6e Mon Sep 17 00:00:00 2001
From: Ebuka Ezike
Date: Fri, 6 Jun 2025 13:15:41 +0100
Subject: [PATCH 1/4] [lldb] add plugin names to process save-core error
output.
-
63 matches
Mail list logo
