jasonmolenda wrote:
I'm also getting back an instruction size of 2 for the 48-bit instruction, in
my unit test, it looks like.
https://github.com/llvm/llvm-project/pull/145793
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llv
https://github.com/jasonmolenda updated
https://github.com/llvm/llvm-project/pull/148105
>From 74995e8f1a982a82bafaa150fb407187fa4b95e4 Mon Sep 17 00:00:00 2001
From: Jason Molenda
Date: Thu, 10 Jul 2025 22:31:54 -0700
Subject: [PATCH 1/4] [lldb][WIP] dump riscv opcode bytes as blocks of 2/4
b
https://github.com/jasonmolenda updated
https://github.com/llvm/llvm-project/pull/148105
>From 74995e8f1a982a82bafaa150fb407187fa4b95e4 Mon Sep 17 00:00:00 2001
From: Jason Molenda
Date: Thu, 10 Jul 2025 22:31:54 -0700
Subject: [PATCH 1/3] [lldb][WIP] dump riscv opcode bytes as blocks of 2/4
b
https://github.com/jasonmolenda updated
https://github.com/llvm/llvm-project/pull/148105
>From 74995e8f1a982a82bafaa150fb407187fa4b95e4 Mon Sep 17 00:00:00 2001
From: Jason Molenda
Date: Thu, 10 Jul 2025 22:31:54 -0700
Subject: [PATCH 1/2] [lldb][WIP] dump riscv opcode bytes as blocks of 2/4
b
jasonmolenda wrote:
I mentioned it last week but I know there was a lot of different comments on
this PR, so I wanted to be more clear about what I was talking about. The
Opcode class is given a Type argument which it uses to decide how to format the
bytes when it Dumps them. But this PR add
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Jason Molenda (jasonmolenda)
Changes
Part of the changes by Ted Woodward et al in
https://github.com/llvm/llvm-project/pull/145793
to change the riscv disassemble --bytes mode output to match llvm-objdump
prints the instruction bytes as seq
https://github.com/jasonmolenda created
https://github.com/llvm/llvm-project/pull/148105
Part of the changes by Ted Woodward et al in
https://github.com/llvm/llvm-project/pull/145793
to change the riscv disassemble --bytes mode output to match llvm-objdump
prints the instruction bytes as sequen
https://github.com/da-viper approved this pull request.
https://github.com/llvm/llvm-project/pull/148037
___
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/13] [lldb] Add DWARFExpressionEntry and
GetExpressi
@@ -2473,3 +2474,35 @@ bool
PluginManager::SetUnwindAssemblyPluginEnabled(llvm::StringRef name,
bool enable) {
return GetUnwindAssemblyInstances().SetInstanceEnabled(name, enable);
}
+
+void PluginManager::AutoCompletePlugin
https://github.com/dmpots updated
https://github.com/llvm/llvm-project/pull/147775
>From c35518e7b221ffbc43b9fb6aa3cbec079bda39b2 Mon Sep 17 00:00:00 2001
From: David Peixotto
Date: Thu, 3 Jul 2025 17:08:27 -0700
Subject: [PATCH 1/2] [lldb] Add completions for plugin list/enable/disable
This c
@@ -2473,3 +2474,35 @@ bool
PluginManager::SetUnwindAssemblyPluginEnabled(llvm::StringRef name,
bool enable) {
return GetUnwindAssemblyInstances().SetInstanceEnabled(name, enable);
}
+
+void PluginManager::AutoCompletePlugin
@@ -2473,3 +2474,35 @@ bool
PluginManager::SetUnwindAssemblyPluginEnabled(llvm::StringRef name,
bool enable) {
return GetUnwindAssemblyInstances().SetInstanceEnabled(name, enable);
}
+
+void PluginManager::AutoCompletePlugin
cjdb wrote:
I think the third option is the best, which will let us control vector and
deque independently.
https://github.com/llvm/llvm-project/pull/139632
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
h
https://github.com/ashgti closed
https://github.com/llvm/llvm-project/pull/147611
___
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-10T10:10:00-07:00
New Revision: 4b6e54a8cf625811f6d817cca284ad87960c2161
URL:
https://github.com/llvm/llvm-project/commit/4b6e54a8cf625811f6d817cca284ad87960c2161
DIFF:
https://github.com/llvm/llvm-project/commit/4b6e54a8cf625811f6d817cca284ad87960c2161.diff
https://github.com/cs01 edited https://github.com/llvm/llvm-project/pull/145382
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
JDevlieghere wrote:
> the green dragon AArch64 bots do run macOS 15.
I don't believe that's accurate. The incremental AS bot is running macOS 14.1
and building against a 14.2 SDK. From the console logs:
```
+ sw_vers
ProductName:macOS
ProductVersion: 14.1
BuildVersion:
https://github.com/ashgti updated
https://github.com/llvm/llvm-project/pull/147611
>From f39b3a47a8b5abadad3709f78ac4aaafc9d9878d Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Tue, 8 Jul 2025 15:44:57 -0700
Subject: [PATCH 1/6] [lldb-dap] Migrate variables request protocol types.
This add
https://github.com/jimingham approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/147603
___
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/147611
>From f39b3a47a8b5abadad3709f78ac4aaafc9d9878d Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Tue, 8 Jul 2025 15:44:57 -0700
Subject: [PATCH 1/5] [lldb-dap] Migrate variables request protocol types.
This add
https://github.com/JDevlieghere edited
https://github.com/llvm/llvm-project/pull/147611
___
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.
LGTM
https://github.com/llvm/llvm-project/pull/147611
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
ashgti wrote:
I added a new helper in JSONUtils for decoding memory references from JSON,
since that is a repeated use case in the protocol POD types. I haven't updated
all the usages yet, but I can do that in a follow up PR.
https://github.com/llvm/llvm-project/pull/147611
___
@@ -238,4 +240,68 @@ CreateExceptionBreakpointFilter(const ExceptionBreakpoint
&bp) {
return filter;
}
+Variable CreateVariable(lldb::SBValue v, int64_t var_ref, bool format_hex,
+bool auto_variable_summaries,
+bool synthetic_
@@ -204,19 +133,20 @@ void VariablesRequestHandler::operator()(
} else {
ashgti wrote:
Done.
https://github.com/llvm/llvm-project/pull/147611
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.l
https://github.com/ashgti updated
https://github.com/llvm/llvm-project/pull/147611
>From f39b3a47a8b5abadad3709f78ac4aaafc9d9878d Mon Sep 17 00:00:00 2001
From: John Harrison
Date: Tue, 8 Jul 2025 15:44:57 -0700
Subject: [PATCH 1/4] [lldb-dap] Migrate variables request protocol types.
This add
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Santhosh Kumar Ellendula (santhoshe447)
Changes
Parse ELF attributes to automatically set disassembler features.
llvm-objdump calls ELFObjectFile::getFeatures, then turns that into a cstr to
pass to createMCSubtargetInfo.
The lldb disassemb
https://github.com/JDevlieghere updated
https://github.com/llvm/llvm-project/pull/147621
>From af54eaf253b1840abb721c3e584d9936fad12c8a Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere
Date: Tue, 8 Jul 2025 16:37:20 -0700
Subject: [PATCH 1/5] [lldb] Document the SBDebugger public interface
Des
Michael137 wrote:
> but there's still 2 data formatter tests failing, not sure what's happening
> there yet.
FWIW, the `object` child of a `std::shared_ptr` should be equivalent to
dereferencing it. How does DIL handle the `$$dereference$$` operator? Does it
do anything special?
https://gith
https://github.com/cmtice updated
https://github.com/llvm/llvm-project/pull/147887
>From 3dbe09deb36a44eb056fa2d3d7dacd341e391697 Mon Sep 17 00:00:00 2001
From: Caroline Tice
Date: Wed, 9 Jul 2025 20:42:03 -0700
Subject: [PATCH] [LLDB] Switch to using DIL as default implementation for
'frame v
https://github.com/kuilpd closed
https://github.com/llvm/llvm-project/pull/147955
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Ilia Kuklin
Date: 2025-07-10T20:34:23+05:00
New Revision: 09fb20ec7d81c1b370dd3d259250c20e505ebeed
URL:
https://github.com/llvm/llvm-project/commit/09fb20ec7d81c1b370dd3d259250c20e505ebeed
DIFF:
https://github.com/llvm/llvm-project/commit/09fb20ec7d81c1b370dd3d259250c20e505ebeed.diff
L
https://github.com/labath approved this pull request.
Cool, thanks.
I'm not totally sure about our ability to break on symbols with no debug info
on all platforms (particularly, windows). If this fails somewhere, you can use
work around this by putting a breakpoint in a file with debug info, t
labath wrote:
@cmtice
https://github.com/llvm/llvm-project/pull/147955
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/walter-erquinigo approved this pull request.
I'm back to review-land. Glad to see this kind of refactors happening :)
https://github.com/llvm/llvm-project/pull/147611
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://
kuilpd wrote:
Added a test without debug info and you're right, it fails without this fix.
https://github.com/llvm/llvm-project/pull/147955
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-c
https://github.com/kuilpd updated
https://github.com/llvm/llvm-project/pull/147955
>From 6b72ecb0f25b34ca112220e8587ef7fea46a38dd Mon Sep 17 00:00:00 2001
From: Ilia Kuklin
Date: Thu, 10 Jul 2025 17:45:15 +0500
Subject: [PATCH 1/2] [LLDB] Check comp_unit before accessing it in DIL
---
lldb/so
https://github.com/da-viper approved this pull request.
https://github.com/llvm/llvm-project/pull/147611
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -204,19 +133,20 @@ void VariablesRequestHandler::operator()(
} else {
da-viper wrote:
var_ref in line 126 also shadows the higher scope.
https://github.com/llvm/llvm-project/pull/147611
___
lldb-commits mailing l
@@ -238,4 +240,68 @@ CreateExceptionBreakpointFilter(const ExceptionBreakpoint
&bp) {
return filter;
}
+Variable CreateVariable(lldb::SBValue v, int64_t var_ref, bool format_hex,
+bool auto_variable_summaries,
+bool synthetic_
@@ -16,7 +18,23 @@ lldb::ValueObjectSP
lldb_private::formatters::GetDesugaredSmartPointerValue(
auto arg = container_type.GetTypeTemplateArgument(0);
if (!arg)
-return nullptr;
+// If there isn't enough debug info, use the pointer type as is
+return ptr.GetSP(
@@ -0,0 +1,168 @@
+//===-- MsvcStlSmartPointer.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
@@ -16,7 +18,23 @@ lldb::ValueObjectSP
lldb_private::formatters::GetDesugaredSmartPointerValue(
auto arg = container_type.GetTypeTemplateArgument(0);
if (!arg)
-return ptr.GetSP(); // FIXME: PDB doesn't have info about template
arguments
+// If there isn't enough
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/147575
>From 8894b65deda77e10ca7c035670d17f2166fd58a7 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Tue, 8 Jul 2025 18:40:06 +0200
Subject: [PATCH 1/7] [LLDB] Add formatters for MSVC STL std::shared_ptr
---
.../Plugin
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 h,cpp --
lldb/include/lldb/Expression/DWARFExpressionList.h
labath wrote:
No debug info in the currently selected frame. Or at least, I think so, based
on looking at the code you're fixing. You can verify that by checking whether
the current code crashes in that scenario. I'm right, it should be sufficient
to build one file with -g0.
`symbols.enable-e
kuilpd wrote:
> It's pretty much an accident we hit this in the test suite. Could you create
> a dedicated test for this. I guess the scenario is "running 'frame var' in a
> frame without debug info" (?)
No debug information at all? Or test the same `settings set
symbols.enable-external-looku
labath wrote:
It's pretty much an accident we hit this in the test suite. Could you create a
dedicated test for this. I guess the scenario is "running 'frame var' in a
frame without debug info" (?)
https://github.com/llvm/llvm-project/pull/147955
___
kuilpd wrote:
I addressed `lldb-shell-subprocess` tests failing in #147955 , but there's
still 2 data formatter tests failing, not sure what's happening there yet.
https://github.com/llvm/llvm-project/pull/147887
___
lldb-commits mailing list
lldb-com
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Ilia Kuklin (kuilpd)
Changes
Check `symbol_context.comp_unit` before accessing it to avoid `nullptr`
dereferencing.
---
Full diff: https://github.com/llvm/llvm-project/pull/147955.diff
1 Files Affected:
- (modified) lldb/source/ValueObj
kuilpd wrote:
`lldb-shell-subprocess` tests were failing because they add a setting `settings
set symbols.enable-external-lookup false`, which disables resolving variables
for compile units, but still marks them as resolved, so
`stack_frame->GetSymbolContext(lldb::eSymbolContextCompUnit)` just
https://github.com/kuilpd created
https://github.com/llvm/llvm-project/pull/147955
Check `symbol_context.comp_unit` before accessing it to avoid `nullptr`
dereferencing.
>From 6b72ecb0f25b34ca112220e8587ef7fea46a38dd Mon Sep 17 00:00:00 2001
From: Ilia Kuklin
Date: Thu, 10 Jul 2025 17:45:15 +
https://github.com/charles-zablit edited
https://github.com/llvm/llvm-project/pull/147768
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Michael137 wrote:
> macOS 15 (Sequoia) is the latest macOS release. This seems pretty aggressive.
> Are any of the bots running macOS 15 at this point? I'm pretty sure
> GreenDragon is not. I'm worried this is equivalent to disabling the tests
> except at people's desk, which means they're goi
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/147575
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -16,7 +18,23 @@ lldb::ValueObjectSP
lldb_private::formatters::GetDesugaredSmartPointerValue(
auto arg = container_type.GetTypeTemplateArgument(0);
if (!arg)
-return nullptr;
+// If there isn't enough debug info, use the pointer type as is
+return ptr.GetSP(
@@ -0,0 +1,168 @@
+//===-- MsvcStlSmartPointer.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,168 @@
+//===-- MsvcStlSmartPointer.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
@@ -16,7 +18,23 @@ lldb::ValueObjectSP
lldb_private::formatters::GetDesugaredSmartPointerValue(
auto arg = container_type.GetTypeTemplateArgument(0);
if (!arg)
-return ptr.GetSP(); // FIXME: PDB doesn't have info about template
arguments
+// If there isn't enough
https://github.com/DrSergei updated
https://github.com/llvm/llvm-project/pull/146950
>From 72921a4039666d58ff68ca2e91d155f91150c7be Mon Sep 17 00:00:00 2001
From: Druzhkov Sergei
Date: Wed, 2 Jul 2025 23:29:26 +0300
Subject: [PATCH] [lldb-dap] Add external terminal support
---
.../test/tools/
labath wrote:
That's correct, and my earlier question basically was what if we make
`CreateHostNativeRegisterContextLinux` return
`NativeRegisterContextLinux_arm64` for arm-on-arm64 debugging. Given that
you're copying a part of _arm64 into _arm32, I am wondering whether the
arm-on-arm64 cas
labath wrote:
> > but I can also imagine doing something like python's "arbitrary width"
> > integers.
>
> Isn't this basically `llvm::APInt` class?
Sort of, but not quite. APInt has an arbitrary but fixed width. Python integers
scale their width dynamically to fit the result (so they sort of
63 matches
Mail list logo
