https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/156987
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/155000
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Aiden Grossman
Date: 2025-09-04T16:56:17-07:00
New Revision: fffe93af52d36a475cf4ee2829261c8aa8b5363f
URL:
https://github.com/llvm/llvm-project/commit/fffe93af52d36a475cf4ee2829261c8aa8b5363f
DIFF:
https://github.com/llvm/llvm-project/commit/fffe93af52d36a475cf4ee2829261c8aa8b5363f.diff
Michael137 wrote:
> We could potentially also drop the char_traits thingy.
Yea was thinking the same. Might do that as a follow-up. That seems like a more
niche use-case, but probably something people do
https://github.com/llvm/llvm-project/pull/156050
_
https://github.com/felipepiovezan closed
https://github.com/llvm/llvm-project/pull/153585
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,51 @@
+"""
+Test that we can backtrace up an ARM Cortex-M Exception return stack
+"""
+
+import lldb
+import json
+from lldbsuite.test.decorators import *
+from lldbsuite.test.lldbtest import *
+from lldbsuite.test import lldbutil
+
+
+class TestCortexMExceptionUnwind(T
https://github.com/rjmccall edited
https://github.com/llvm/llvm-project/pull/97443
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -2243,9 +2236,27 @@
ItaniumRecordLayoutBuilder::updateExternalFieldOffset(const FieldDecl *Field,
uint64_t ComputedOffset)
{
uint64_t ExternalFieldOffset = External.getExternalFieldOffset(Field);
- if (InferAlignmen
https://github.com/jeffreytan81 edited
https://github.com/llvm/llvm-project/pull/156803
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -327,6 +366,11 @@ serveConnection(const Socket::SocketProtocol &protocol,
const std::string &name,
std::unique_lock lock(dap_sessions_mutex);
dap_sessions.erase(&loop);
std::notify_all_at_thread_exit(dap_sessions_condition, std::move(lock));
+
+ // St
Author: Adrian Prantl
Date: 2025-09-05T15:47:04-07:00
New Revision: 7c5b535d8c50e52ba13439ce52b9fe6fa34afcab
URL:
https://github.com/llvm/llvm-project/commit/7c5b535d8c50e52ba13439ce52b9fe6fa34afcab
DIFF:
https://github.com/llvm/llvm-project/commit/7c5b535d8c50e52ba13439ce52b9fe6fa34afcab.diff
https://github.com/adrian-prantl closed
https://github.com/llvm/llvm-project/pull/157192
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
jasonmolenda wrote:
Thanks. I've asked someone with access to a Windows system to help me
understand if this is an issue with my new yaml2macho-core utility (producing
incorrect corefiles) or a problem with lldb on Windows reading (32-bit?) mach-o
corefiles, I'll hold off on tweaking this any
@@ -327,6 +366,11 @@ serveConnection(const Socket::SocketProtocol &protocol,
const std::string &name,
std::unique_lock lock(dap_sessions_mutex);
dap_sessions.erase(&loop);
std::notify_all_at_thread_exit(dap_sessions_condition, std::move(lock));
+
+ // St
lexi-nadia wrote:
https://github.com/llvm/llvm-project/pull/157150 is already approved - I'm just
waiting for someone to merge it and/or for my own commit access to be granted.
:)
https://github.com/llvm/llvm-project/pull/156956
___
lldb-commits mail
https://github.com/lexi-nadia created
https://github.com/llvm/llvm-project/pull/157178
None
>From 088a1dd896e7bbb27e4be3a59fd241928e0fccfd Mon Sep 17 00:00:00 2001
From: lexinadia
Date: Fri, 5 Sep 2025 17:40:29 +
Subject: [PATCH 1/4] Default-initialize all fields of
lldb_dap::protocol::Sy
https://github.com/lexi-nadia updated
https://github.com/llvm/llvm-project/pull/157150
>From 088a1dd896e7bbb27e4be3a59fd241928e0fccfd Mon Sep 17 00:00:00 2001
From: lexinadia
Date: Fri, 5 Sep 2025 17:40:29 +
Subject: [PATCH 1/3] Default-initialize all fields of
lldb_dap::protocol::Symbol.
Author: lexi-nadia
Date: 2025-09-05T13:51:49-07:00
New Revision: a652979b483da6e5a45ebf6428be408de66ac857
URL:
https://github.com/llvm/llvm-project/commit/a652979b483da6e5a45ebf6428be408de66ac857
DIFF:
https://github.com/llvm/llvm-project/commit/a652979b483da6e5a45ebf6428be408de66ac857.diff
LO
https://github.com/ashgti closed
https://github.com/llvm/llvm-project/pull/157150
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
ashgti wrote:
I'll send an update to initialize all the variables.
https://github.com/llvm/llvm-project/pull/156956
___
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 (GeorgeHuyubo)
Changes
This change improves how LLDB's ProcessElfCore plugin identifies the main
executable when loading ELF core files. Previously, the code would simply use
the first entry in the NT_FILE section, which is not guaran
https://github.com/GeorgeHuyubo ready_for_review
https://github.com/llvm/llvm-project/pull/157170
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/lexi-nadia updated
https://github.com/llvm/llvm-project/pull/157150
>From 088a1dd896e7bbb27e4be3a59fd241928e0fccfd Mon Sep 17 00:00:00 2001
From: lexinadia
Date: Fri, 5 Sep 2025 17:40:29 +
Subject: [PATCH 1/3] Default-initialize all fields of
lldb_dap::protocol::Symbol.
@@ -2243,9 +2236,27 @@
ItaniumRecordLayoutBuilder::updateExternalFieldOffset(const FieldDecl *Field,
uint64_t ComputedOffset)
{
uint64_t ExternalFieldOffset = External.getExternalFieldOffset(Field);
- if (InferAlignmen
charles-zablit wrote:
> LLDB reviewer here, I am not very familiar with Python typing but -
>
> > We from **future** import annotations at the start of cindex.py which lets
> > us use the PEP 585 features (among others) even in Pyhon 3.8.
>
> Can we do this in the lldb file as well? When the m
https://github.com/lexi-nadia updated
https://github.com/llvm/llvm-project/pull/157150
>From 088a1dd896e7bbb27e4be3a59fd241928e0fccfd Mon Sep 17 00:00:00 2001
From: lexinadia
Date: Fri, 5 Sep 2025 17:40:29 +
Subject: [PATCH 1/2] Default-initialize all fields of
lldb_dap::protocol::Symbol.
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: None (lexi-nadia)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/157150.diff
2 Files Affected:
- (modified) lldb/tools/lldb-dap/Handler/ModuleSymbolsRequestHandler.cpp (+1-1)
- (modified) lldb/tools/lldb-dap/Protocol/
https://github.com/JDevlieghere approved this pull request.
LGTM!
https://github.com/llvm/llvm-project/pull/157150
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/jeffreytan81 requested changes to this pull request.
For the comment I left.
https://github.com/llvm/llvm-project/pull/156803
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/l
cjdb wrote:
Ping
https://github.com/llvm/llvm-project/pull/139632
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/maryammo edited
https://github.com/llvm/llvm-project/pull/157152
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -65,6 +203,170 @@ public:
using iterator = pointer;
using const_iterator = const_pointer;
+public:
+ _LIBCPP_CONSTEXPR_SINCE_CXX20 _LIBCPP_HIDE_FROM_ABI
__split_buffer_size_layout() = default;
+
+ _LIBCPP_CONSTEXPR_SINCE_CXX20 _L
https://github.com/maryammo edited
https://github.com/llvm/llvm-project/pull/157152
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -50,29 +50,29 @@ llvm::json::Value toJSON(const SourceLLDBData &);
struct Symbol {
/// The symbol id, usually the original symbol table index.
- uint32_t id;
+ uint32_t id = 0;
/// True if this symbol is debug information in a symbol.
- bool isDebug;
+ bool isDeb
https://github.com/maryammo created
https://github.com/llvm/llvm-project/pull/157152
None
>From fca9c5ba81d3f06c4c0ee49ca37f45872c87bb54 Mon Sep 17 00:00:00 2001
From: Maryam Moghadas
Date: Fri, 5 Sep 2025 17:31:12 +
Subject: [PATCH] [Clang][PowerPC] Add __dmr2048 type and DMF crypto built
dsandersllvm wrote:
> For testing the endianess, I'm not sure we have PPC LLDB buildbots that would
> test this (@DavidSpickett or @JDevlieghere might know). Any chance this can
> be tested with unit-tests somehow? Maybe we can just pass an LLVM IR module
> into the IRInterpreter? We could pot
@@ -644,7 +723,25 @@ bool IRInterpreter::CanInterpret(llvm::Module &module,
llvm::Function &function,
switch (operand_type->getTypeID()) {
default:
break;
-case Type::FixedVectorTyID:
+case Type::FixedVectorTyID: {
dsa
walter-erquinigo wrote:
@royitaqi , watch for flaky issues these days just in case
https://github.com/llvm/llvm-project/pull/156231
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -62,7 +97,11 @@ struct Variables {
/// These are the variables evaluated from debug console REPL.
llvm::DenseMap m_referencedpermanent_variables;
- int64_t m_next_temporary_var_ref{VARREF_FIRST_VAR_IDX};
+ /// Key = frame_id
+ /// Value = (locals, globals Registers)
@@ -62,7 +97,11 @@ struct Variables {
/// These are the variables evaluated from debug console REPL.
llvm::DenseMap m_referencedpermanent_variables;
- int64_t m_next_temporary_var_ref{VARREF_FIRST_VAR_IDX};
+ /// Key = frame_id
+ /// Value = (locals, globals Registers)
dwblaikie wrote:
Thanks for all the work and lessons learned - I was rather looking forward
to/hoping that a unification of Clang header modules/serialized AST loading
with LLDB's needs would be a great chance to align incentives/reduce
variation/etc - sorry to hear it didn't pan out :/
http
https://github.com/charles-zablit closed
https://github.com/llvm/llvm-project/pull/156868
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Charles Zablit
Date: 2025-09-05T17:25:38+01:00
New Revision: 25ebdfe0ab202a6cb30232d84bc5838439fd67d5
URL:
https://github.com/llvm/llvm-project/commit/25ebdfe0ab202a6cb30232d84bc5838439fd67d5
DIFF:
https://github.com/llvm/llvm-project/commit/25ebdfe0ab202a6cb30232d84bc5838439fd67d5.diff
Author: Jonas Devlieghere
Date: 2025-09-05T09:24:59-07:00
New Revision: 65a7317234680045b045f3c4155b647faeae4304
URL:
https://github.com/llvm/llvm-project/commit/65a7317234680045b045f3c4155b647faeae4304
DIFF:
https://github.com/llvm/llvm-project/commit/65a7317234680045b045f3c4155b647faeae4304.d
https://github.com/JDevlieghere approved this pull request.
https://github.com/llvm/llvm-project/pull/156648
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -644,7 +723,25 @@ bool IRInterpreter::CanInterpret(llvm::Module &module,
llvm::Function &function,
switch (operand_type->getTypeID()) {
default:
break;
-case Type::FixedVectorTyID:
+case Type::FixedVectorTyID: {
Mic
https://github.com/JDevlieghere approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/156868
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
mizvekov wrote:
> I noticed that some tests are dropped in the PR, esp. eg. in the AST
> unittests. Did you check the test coverage if that wouldn't shrink due to
> those removals? In the ASTImporter I remember a few years ago we added some
> tests to exercise the uncovered ctors and getters o
https://github.com/tgs-sc updated
https://github.com/llvm/llvm-project/pull/154123
>From 5272b4fefd24e34b142a275592e27a5244488fd6 Mon Sep 17 00:00:00 2001
From: Timur Golubovich
Date: Mon, 18 Aug 2025 17:29:01 +0300
Subject: [PATCH] [lldb][DWARFASTParserClang] Added a check for the
specializat
jimingham wrote:
I don't remember how that works in swift, but note, there are two separate
issues with the C family expression parser. One was making local declarations
override ivar references in name resolution in the context of the expression.
That is why we inject variables into the exp
Michael137 wrote:
> Any word on this? Dead/can't be done? Lowered priority/might revisit later?
> Any conclusions/lessons that'd be handy to record for posterity?
The performance implications of the way this was implemented turned out to be
quite difficult to overcome. The way we wanted to add
https://github.com/charles-zablit edited
https://github.com/llvm/llvm-project/pull/156868
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/charles-zablit updated
https://github.com/llvm/llvm-project/pull/156868
>From 54f31b5cc3ec31e53e457c1879887f54ff14f14e Mon Sep 17 00:00:00 2001
From: Charles Zablit
Date: Fri, 5 Sep 2025 12:01:56 +0100
Subject: [PATCH] [lldb] fix Python 3.9+ specific typing annotations
---
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 origin/main...HEAD
lldb/packages/Python/lldbsuite/test/decorators.py
``
:warning:
https://github.com/charles-zablit updated
https://github.com/llvm/llvm-project/pull/156868
>From 46503ba1ddcaae5ad7cfd283111e8e586da0855a Mon Sep 17 00:00:00 2001
From: Charles Zablit
Date: Thu, 4 Sep 2025 14:18:02 +0100
Subject: [PATCH] [lldb] remove Python 3.9 specific typing annotations
---
https://github.com/Michael137 requested changes to this pull request.
Marking as needs changes so we don't forget to move the PDB support code into
LLVM
https://github.com/llvm/llvm-project/pull/149701
___
lldb-commits mailing list
lldb-commits@lists.
https://github.com/Michael137 commented:
For testing the endianess, I'm not sure we have PPC LLDB buildbots that would
test this (@DavidSpickett or @JDevlieghere might know). Any chance this can be
tested with unit-tests somehow? Any chance we can just pass an LLVM IR module
into the IRInterpr
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/155000
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
carlosgalvezp wrote:
> I opened an RFC pitch thread on the forums.
For easier access:
https://discourse.llvm.org/t/rfc-inclusive-language-migrate-sanity-checks-to-soundness-checks
https://github.com/llvm/llvm-project/pull/156995
___
lldb-commits mail
@@ -367,7 +379,67 @@ class InterpreterStackFrame {
return true;
}
- bool ResolveConstant(lldb::addr_t process_address, const Constant *constant)
{
+ bool ResolveVectorConstant(lldb::addr_t process_address,
+ const Constant *constant,
+
llvmbot wrote:
/pull-request llvm/llvm-project#157048
https://github.com/llvm/llvm-project/pull/156050
___
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.
We could potentially also drop the char_traits thingy.
https://github.com/llvm/llvm-project/pull/156050
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailm
@@ -1564,7 +1660,103 @@ bool IRInterpreter::Interpret(llvm::Module &module,
llvm::Function &function,
returnVal = value.GetScalar();
// Push the return value as the result
-frame.AssignValue(inst, returnVal, module);
+frame.AssignValue(inst, re
j2kun wrote:
Maybe "spot check" instead of "sanity check", though "spot" is not a
replacement for "sanity" generally
https://github.com/llvm/llvm-project/pull/156995
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-
64 matches
Mail list logo
