https://github.com/satyajanga updated
https://github.com/llvm/llvm-project/pull/149019
>From 1a8ecb925c19f3c637838ea6cea2c8bb640e86d5 Mon Sep 17 00:00:00 2001
From: Jeffrey Tan
Date: Wed, 21 Jul 2021 13:32:56 -0700
Subject: [PATCH] New DynamicLoaderDumpWithModuleList for coredump debugging
Sum
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/source/Plugins/DynamicLoader/ModuleList-DYLD/D
https://github.com/MaskRay approved this pull request.
https://github.com/llvm/llvm-project/pull/149015
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/satyajanga created
https://github.com/llvm/llvm-project/pull/149019
Summary:
This patch adds a new `DynamicLoaderDumpWithModuleList` plugin which can be
used for coredump debugging. It leverages NT_FILE note in coredump to get
module list instead of relying on posix rdebug d
https://github.com/satyajanga updated
https://github.com/llvm/llvm-project/pull/148735
>From c021e054277a590901012e6c9fcdcff8fedf9867 Mon Sep 17 00:00:00 2001
From: Jeffrey Tan
Date: Wed, 21 Jul 2021 13:32:56 -0700
Subject: [PATCH] Add new "target module replace" command
Summary:
For dump debu
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Chelsea Cassanova (chelcassanova)
Changes
In LLDB RPC, we need to keep track of methods that have a pointer parameter
followed by a lengtgh parameter as these parameters need some exceptions when
they're being emitted by lldb-rpc-gen. Prev
https://github.com/chelcassanova created
https://github.com/llvm/llvm-project/pull/148981
In LLDB RPC, we need to keep track of methods that have a pointer parameter
followed by a lengtgh parameter as these parameters need some exceptions when
they're being emitted by lldb-rpc-gen. Previously,
https://github.com/royitaqi updated
https://github.com/llvm/llvm-project/pull/148738
>From 890eb98ceada6495f6a089f7f0a4823b7369d2ec Mon Sep 17 00:00:00 2001
From: royshi
Date: Mon, 14 Jul 2025 13:45:13 -0700
Subject: [PATCH 1/2] [lldb] Fix a crash in lldb-server during
RemoveSoftwareBreakpoint
dmpots wrote:
Follow up PR to fix a buildbot failure: #148956
https://github.com/llvm/llvm-project/pull/147775
___
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 Peixotto (dmpots)
Changes
The plugins completion test was checking completions for the abi plugins. But
the available abi plugins will depend on which
[targets](https://github.com/llvm/llvm-project/blob/42d2ae1034b287eb60563c370dbf52
dmpots wrote:
This is to fix a buildbot failure:
https://lab.llvm.org/buildbot/#/builders/195/builds/11884
https://github.com/llvm/llvm-project/pull/148956
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailma
https://github.com/dmpots created
https://github.com/llvm/llvm-project/pull/148956
The plugins completion test was checking completions for the abi plugins. But
the available abi plugins will depend on which
[targets](https://github.com/llvm/llvm-project/blob/42d2ae1034b287eb60563c370dbf52c59b
https://github.com/dmpots closed
https://github.com/llvm/llvm-project/pull/147775
___
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 `hip-third-party-libs-test`
running on `ext_buildbot_hw_05-hip-docker` while building
`clang-tools-extra,clang,lldb,llvm` at step 4 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/206/builds
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`llvm-clang-x86_64-sie-ubuntu-fast` running on `sie-linux-worker` while
building `clang-tools-extra,clang,lldb,llvm` at step 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/144/b
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-hip-vega20` running
on `hip-vega20-0` while building `clang-tools-extra,clang,lldb,llvm` at step 3
"annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/123/builds/23431
Here is the relev
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-cmake-x86_64-avx512-linux` running on `avx512-intel64` while building
`clang-tools-extra,clang,lldb,llvm` at step 6 "build stage 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/133/builds/196
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`openmp-offload-amdgpu-runtime-2` running on `rocm-worker-hw-02` while building
`clang-tools-extra,clang,lldb,llvm` at step 5 "compile-openmp".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/10/builds/
jansvoboda11 wrote:
Windows CI failure look unrelated.
https://github.com/llvm/llvm-project/pull/146422
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: David Peixotto
Date: 2025-07-15T12:44:00-07:00
New Revision: fccae859bc949ba390184614e07234267a734b86
URL:
https://github.com/llvm/llvm-project/commit/fccae859bc949ba390184614e07234267a734b86
DIFF:
https://github.com/llvm/llvm-project/commit/fccae859bc949ba390184614e07234267a734b86.diff
@@ -1321,10 +1321,11 @@ enum CompletionType {
eTypeCategoryNameCompletion = (1ul << 24),
eCustomCompletion = (1ul << 25),
eThreadIDCompletion = (1ul << 26),
+ eManagedPluginCompletion = (1ul << 27),
// This last enum element is just for input validation.
// Add new
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: None (cmtice)
Changes
The lldb-x86_64-win buildbot is failing on this one DIL test. Disable the test
on Windows until we can debug it on Windows.
---
Full diff: https://github.com/llvm/llvm-project/pull/148940.diff
1 Files Affected:
- (
https://github.com/cmtice created
https://github.com/llvm/llvm-project/pull/148940
The lldb-x86_64-win buildbot is failing on this one DIL test. Disable the test
on Windows until we can debug it on Windows.
>From 83094baf1eb1969e66c1a458ef7c29d2b1c3ef7f Mon Sep 17 00:00:00 2001
From: Caroline
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: nerix (Nerixyz)
Changes
This PR converts the `std::variant` summary from Python to C++.
Split from #148554. MSVC's STL and libstdc++ use the same type name for
`std::variant`, thus they need one "dispatcher" function that checks the type
https://github.com/Nerixyz created
https://github.com/llvm/llvm-project/pull/148929
This PR converts the `std::variant` summary from Python to C++.
Split from #148554. MSVC's STL and libstdc++ use the same type name for
`std::variant`, thus they need one "dispatcher" function that checks the t
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: None (jimingham)
Changes
…(#144919)"
This was causing a couple of failures on the Ubuntu bots. Reverting while we
wait on a fix for those issues.
This reverts commit 8612926c306c5191a5fb385dd11467728c59e982.
---
Full diff: https://github
https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/148691
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: nerix
Date: 2025-07-15T11:38:43-07:00
New Revision: 95fa67603c4ab5d75a2f8df328d7da5580466d50
URL:
https://github.com/llvm/llvm-project/commit/95fa67603c4ab5d75a2f8df328d7da5580466d50
DIFF:
https://github.com/llvm/llvm-project/commit/95fa67603c4ab5d75a2f8df328d7da5580466d50.diff
LOG: [L
Nerixyz wrote:
I can't merge this on my own, could you merge this for me please? @JDevlieghere
https://github.com/llvm/llvm-project/pull/148691
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/l
https://github.com/benlangmuir approved this pull request.
LGTM, thanks!
https://github.com/llvm/llvm-project/pull/146422
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/147538
>From 9f719389412467375cbd4c51ec970fc16da3d54d Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Sat, 21 Jun 2025 17:35:23 +0200
Subject: [PATCH 1/3] [LLDB] Add formatters for MSVC STL std::vector
---
.../Plugins/L
https://github.com/jansvoboda11 updated
https://github.com/llvm/llvm-project/pull/146422
>From 69049bfcd81134f3787d1ee14ab3e5c6d91eb87d Mon Sep 17 00:00:00 2001
From: Jan Svoboda
Date: Thu, 3 Jul 2025 12:46:58 -0700
Subject: [PATCH 1/4] [clang][modules] Serialize `CodeGenOptions`
---
clang-to
jimingham wrote:
Actually, the test will be a little harder than that because the deadlock comes
between the main lldb work and async work done by the status line. So my test,
which just runs lldb in Python, wouldn't have shown that error.
I wonder if it would be possible to have a version of
@@ -36,13 +36,13 @@ void CodeGenOptions::resetNonModularOptions(StringRef
ModuleFormat) {
// emitted into the PCM (-gmodules).
if (ModuleFormat == "raw" && !DebugTypeExtRefs) {
#define DEBUGOPT(Name, Bits, Default, Compatibility)
\
- if constexp
https://github.com/JDevlieghere edited
https://github.com/llvm/llvm-project/pull/148708
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -46,13 +46,32 @@ class CodeGenOptionsBase {
enum class CompatibilityKind {
/// Does affect the construction of the AST in a way that does prevent
/// module interoperability.
-Affecting,
+NotCompatible,
+/// Does affect the construction of the AST in a
jimingham wrote:
The revert was:
https://github.com/llvm/llvm-project/pull/148915
Good hunting!
https://github.com/llvm/llvm-project/pull/144919
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo
https://github.com/jimingham created
https://github.com/llvm/llvm-project/pull/148915
…(#144919)"
This was causing a couple of failures on the Ubuntu bots. Reverting while we
wait on a fix for those issues.
This reverts commit 8612926c306c5191a5fb385dd11467728c59e982.
>From f7ebd7ec19a2099e6
https://github.com/jimingham closed
https://github.com/llvm/llvm-project/pull/148915
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: jimingham
Date: 2025-07-15T11:04:04-07:00
New Revision: bcd0a7ae2a3ae81545190a0b2796eb63656b5d42
URL:
https://github.com/llvm/llvm-project/commit/bcd0a7ae2a3ae81545190a0b2796eb63656b5d42
DIFF:
https://github.com/llvm/llvm-project/commit/bcd0a7ae2a3ae81545190a0b2796eb63656b5d42.diff
LOG
athierry-oct wrote:
@jimingham Yes can you revert it please, while I figure this out?
Thank you
https://github.com/llvm/llvm-project/pull/144919
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/
jimingham wrote:
@athierry-oct - this patch seems to have caused some failures on the ubuntu
bot. If you think you can resolve those failures quickly, then please do. If
you aren't able to do that give me a ping and I'll revert this till you can
figure this out.
https://github.com/llvm/llvm
https://github.com/jimingham approved this pull request.
Thanks for catching this. Keeping the module list locked too long is one of
the easiest ways to produce deadlocks in lldb at present!
I can't see a reason why the work done when lldb is notified of a new module
should require that the m
chelcassanova wrote:
I've undrafted this PR and updated the [design
doc](https://github.com/llvm/llvm-project/pull/138612) to reflect what the
client-side emitters are doing here.
@DavidSpickett Would you able to take a look at this PR and the updated design
doc when you can?
https://github.
https://github.com/chelcassanova edited
https://github.com/llvm/llvm-project/pull/147655
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/147538
>From d8a898b9a3f6b16d551baa7253344402d75ca4d8 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Sat, 21 Jun 2025 17:35:23 +0200
Subject: [PATCH 1/3] [LLDB] Add formatters for MSVC STL std::vector
---
.../Plugins/L
https://github.com/chelcassanova updated
https://github.com/llvm/llvm-project/pull/138612
>From 3d29af3b776c407de606cf507c9b03c49daa11b0 Mon Sep 17 00:00:00 2001
From: Chelsea Cassanova
Date: Wed, 30 Apr 2025 09:04:40 -0700
Subject: [PATCH] [lldb][RPC] Design doc for upstreaming PR
This mainly
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/21064
Here is the relevant piece of the b
@@ -539,6 +540,8 @@ static Status HandleFileAction(ProcessLaunchInfo
&launch_info,
: "unable to launch");
}
+ [env_dict release];
+ [options release];
kastiglione wrote:
I wonder if these objc++ files ca
@@ -289,12 +286,8 @@ void LanguageRuntime::InitializeCommands(CommandObject
*parent) {
if (!parent->IsMultiwordObject())
return;
- LanguageRuntimeCreateInstance create_callback;
-
for (uint32_t idx = 0;
- (create_callback =
-PluginManager::GetLangu
clayborg wrote:
> > Unfortunately there is no easy way to add testing for this. No RISCV
> > hardware at the disposal. I welcome the suggestions.
>
> Make a core file that does not include any internal data and then it can be
> tested on any system. If you have to satisfy internal policies aro
dmpots wrote:
Would it be possible to add a test that triggers this bug? It looks like a
fairly simple scenario that launches lldb-server and then attaches to it. Seems
like good coverage to have in the test if we don't already. Also, is this a
100% reproducable deadlock or is it somewhat non-
@@ -57,11 +57,12 @@ class EmulateInstructionRISCV : public EmulateInstruction {
static bool SupportsThisInstructionType(InstructionType inst_type) {
switch (inst_type) {
-case eInstructionTypeAny:
-case eInstructionTypePCModifying:
+case lldb_private::eInstru
https://github.com/satyajanga converted_to_draft
https://github.com/llvm/llvm-project/pull/147434
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dmpots wrote:
@jimingham we found a deadlock that we suspect is related to this patch. Please
take a look at the proposed fix in #148774. Thanks!
https://github.com/llvm/llvm-project/pull/146441
___
lldb-commits mailing list
lldb-commits@lists.llvm.or
jimingham wrote:
> From the issue, we can have persistent assembly source breakpoint if it is
> set from the disassembly view.
>
> We only create sourceReference and virtual disassembly file if there is no
> source file for that frame.
>
> we can store the necessary information in the adapter
https://github.com/royitaqi edited
https://github.com/llvm/llvm-project/pull/148738
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
github-actions[bot] wrote:
@athierry-oct Congratulations on having your first Pull Request (PR) merged
into the LLVM Project!
Your changes will be combined with recent changes from other authors, then
tested by our [build bots](https://lab.llvm.org/buildbot/). If there is a
problem with a b
Author: athierry-oct
Date: 2025-07-15T09:33:00-07:00
New Revision: 8612926c306c5191a5fb385dd11467728c59e982
URL:
https://github.com/llvm/llvm-project/commit/8612926c306c5191a5fb385dd11467728c59e982
DIFF:
https://github.com/llvm/llvm-project/commit/8612926c306c5191a5fb385dd11467728c59e982.diff
https://github.com/jimingham closed
https://github.com/llvm/llvm-project/pull/144919
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
jimingham wrote:
It doesn't look like there are any outstanding emendations. Pushing.
https://github.com/llvm/llvm-project/pull/144919
___
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/148738
___
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/148738
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/147538
>From d8a898b9a3f6b16d551baa7253344402d75ca4d8 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Sat, 21 Jun 2025 17:35:23 +0200
Subject: [PATCH 1/2] [LLDB] Add formatters for MSVC STL std::vector
---
.../Plugins/L
https://github.com/clayborg commented:
This patch looks good to me unless we are trying to protect the ModuleList
contents during the notification to ensure it doesn't change before the
notification has been delivered. Jim and Jonas? Thoughts?
https://github.com/llvm/llvm-project/pull/148774
_
https://github.com/Michael137 closed
https://github.com/llvm/llvm-project/pull/148548
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: nerix
Date: 2025-07-15T17:17:28+01:00
New Revision: eec98bef84b8a68533d9176468c1d2010f26717f
URL:
https://github.com/llvm/llvm-project/commit/eec98bef84b8a68533d9176468c1d2010f26717f
DIFF:
https://github.com/llvm/llvm-project/commit/eec98bef84b8a68533d9176468c1d2010f26717f.diff
LOG: [L
https://github.com/Michael137 approved this pull request.
https://github.com/llvm/llvm-project/pull/148548
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Michael137 approved this pull request.
https://github.com/llvm/llvm-project/pull/147538
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/clayborg approved this pull request.
https://github.com/llvm/llvm-project/pull/147775
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -1321,10 +1321,11 @@ enum CompletionType {
eTypeCategoryNameCompletion = (1ul << 24),
eCustomCompletion = (1ul << 25),
eThreadIDCompletion = (1ul << 26),
+ eManagedPluginCompletion = (1ul << 27),
// This last enum element is just for input validation.
// Add new
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 01/16] Fix logs, prevent accidentally printing a partial read
whe
@@ -106,17 +112,17 @@ add_dependencies(liblldb-resource-headers
liblldb-header-staging)
add_dependencies(liblldb liblldb-resource-headers)
# Take the headers from the staging directory and fix up their includes for
the framework.
-# Then write them to the output directory.
+
@@ -249,6 +250,41 @@ static unsigned GetCXXMethodCVQuals(const DWARFDIE
&subprogram,
return cv_quals;
}
+// TODO:
+// 0. Adjust FindInSymbols
+// 1. log failure paths
+// 2. What happens for functions without a linkage name? Previously we didn't
+// attach a label for those
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/Expression.h lldb/incl
https://github.com/Michael137 created
https://github.com/llvm/llvm-project/pull/148877
None
>From 7f805d67f73d9683d69410895be1d042f0c6da14 Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Fri, 15 Nov 2024 01:59:36 +
Subject: [PATCH] [lldb][Expression] Encode Module and DIE UIDs into funct
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/148285
>From 104fbb9daa6ea0d4483939662ae08a8d42d77f44 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Fri, 11 Jul 2025 22:06:47 +0200
Subject: [PATCH 1/3] [LLDB] Add formatters for MSVC STL std::(forward_)list
---
lldb/
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/148285
>From 104fbb9daa6ea0d4483939662ae08a8d42d77f44 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Fri, 11 Jul 2025 22:06:47 +0200
Subject: [PATCH 1/3] [LLDB] Add formatters for MSVC STL std::(forward_)list
---
lldb/
@@ -1642,19 +1662,34 @@ static void
LoadCommonStlFormatters(lldb::TypeCategoryImplSP cpp_category_sp) {
},
"MSVC STL/libstdc++ std::wstring summary provider"));
+ stl_summary_flags.SetDontShowChildren(false);
+ stl_summary_flags.SetSkipPointers(false);
+
https://github.com/cmtice closed
https://github.com/llvm/llvm-project/pull/147887
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: cmtice
Date: 2025-07-15T08:19:10-07:00
New Revision: f5c676d6d95dc63b8dcb43dd2e4dfc913a9c5a50
URL:
https://github.com/llvm/llvm-project/commit/f5c676d6d95dc63b8dcb43dd2e4dfc913a9c5a50
DIFF:
https://github.com/llvm/llvm-project/commit/f5c676d6d95dc63b8dcb43dd2e4dfc913a9c5a50.diff
LOG: [
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/148285
>From 104fbb9daa6ea0d4483939662ae08a8d42d77f44 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Fri, 11 Jul 2025 22:06:47 +0200
Subject: [PATCH 1/3] [LLDB] Add formatters for MSVC STL std::(forward_)list
---
lldb/
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 1/4] [LLDB] Switch to using DIL as default implementation for
'fra
https://github.com/Nerixyz edited
https://github.com/llvm/llvm-project/pull/148285
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/148285
>From 104fbb9daa6ea0d4483939662ae08a8d42d77f44 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Fri, 11 Jul 2025 22:06:47 +0200
Subject: [PATCH 1/3] [LLDB] Add formatters for MSVC STL std::(forward_)list
---
lldb/
@@ -1642,19 +1662,34 @@ static void
LoadCommonStlFormatters(lldb::TypeCategoryImplSP cpp_category_sp) {
},
"MSVC STL/libstdc++ std::wstring summary provider"));
+ stl_summary_flags.SetDontShowChildren(false);
+ stl_summary_flags.SetSkipPointers(false);
+
https://github.com/tedwoodward approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/148823
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/148285
>From 104fbb9daa6ea0d4483939662ae08a8d42d77f44 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Fri, 11 Jul 2025 22:06:47 +0200
Subject: [PATCH 1/3] [LLDB] Add formatters for MSVC STL std::(forward_)list
---
lldb/
da-viper wrote:
>From the issue, we can have persistent assembly source breakpoint if it is set
>from the disassembly view.
We only create sourceReference and virtual disassembly file if there is no
source file for that frame.
we can store the necessary information in the adapter data to re
athierry-oct wrote:
Gentle ping — is this PR ready to merge? I don’t have merge privileges, so if
one of the reviewers could take care of it when it's ready, I’d appreciate it!
https://github.com/llvm/llvm-project/pull/144919
___
lldb-commits mailing
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/147538
>From 2ca001ffd2c84410877680d832af2effbc560dde Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Sat, 21 Jun 2025 17:35:23 +0200
Subject: [PATCH 1/2] [LLDB] Add formatters for MSVC STL std::vector
---
.../Plugins/L
@@ -1656,9 +1658,6 @@ static void
LoadCommonStlFormatters(lldb::TypeCategoryImplSP cpp_category_sp) {
},
"MSVC STL/libstdc++ std::wstring summary provider"));
- stl_summary_flags.SetDontShowChildren(false);
Nerixyz wrote:
I didn't rebase
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/148548
>From 9950cdb7fa60c9ef3f284e7d091c2afb3a5f7aa6 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Sun, 13 Jul 2025 22:46:23 +0200
Subject: [PATCH] [LLDB] Add formatters for MSVC STL std::tuple
---
.../Plugins/Langua
@@ -188,267 +241,326 @@ def validate_response(cls, command, response):
)
def _read_packet_thread(self):
-done = False
try:
-while not done:
+while True:
packet = read_packet(self.recv, trace_file=self.tr
@@ -188,267 +241,326 @@ def validate_response(cls, command, response):
)
def _read_packet_thread(self):
-done = False
try:
-while not done:
+while True:
packet = read_packet(self.recv, trace_file=self.tr
@@ -1141,15 +1253,22 @@ def request_completions(self, text, frameId=None):
"type": "request",
"arguments": args_dict,
}
-return self.send_recv(command_dict)
-
-def request_modules(self, startModule: int, moduleCount: int):
-re
@@ -152,25 +189,41 @@ def __init__(
self.log_file = log_file
self.send = send
self.recv = recv
-self.recv_packets: list[Optional[ProtocolMessage]] = []
-self.recv_condition = threading.Condition()
-self.recv_thread = threading.Thr
@@ -1141,15 +1253,22 @@ def request_completions(self, text, frameId=None):
"type": "request",
"arguments": args_dict,
}
-return self.send_recv(command_dict)
-
-def request_modules(self, startModule: int, moduleCount: int):
-re
@@ -1376,29 +1376,26 @@ class EntityRegister : public Materializer::Entity {
return;
}
-DataExtractor register_data;
-
-if (!reg_value.GetData(register_data)) {
- err = Status::FromErrorStringWithFormat(
- "couldn't get the data for register %s"
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: David Spickett (DavidSpickett)
Changes
Relates to https://github.com/llvm/llvm-project/issues/135707
Where it was reported that reading the PC using "register read" had different
results to an expression "$pc".
This was happening because
1 - 100 of 115 matches
Mail list logo
