llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Daniel Sanders (dsandersllvm)
Changes
The test for this is artificial as I'm not aware of any upstream targets that
use DW_CFA_val_offset
RegisterContextUnwind::ReadFrameAddress now reports how it's attempting to
obtain the CFA unless all
https://github.com/dsandersllvm created
https://github.com/llvm/llvm-project/pull/150732
The test for this is artificial as I'm not aware of any upstream targets that
use DW_CFA_val_offset
RegisterContextUnwind::ReadFrameAddress now reports how it's attempting to
obtain the CFA unless all suc
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `fuchsia-x86_64-linux`
running on `fuchsia-debian-64-us-central1-a-1` while building `lldb` at step 4
"annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/11/builds/20409
Here is the relevant p
https://github.com/JDevlieghere updated
https://github.com/llvm/llvm-project/pull/148994
>From a4034e2f0948bfa61bfbf681bd5d9355aeb09beb Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere
Date: Tue, 15 Jul 2025 16:54:05 -0700
Subject: [PATCH] [lldb] Always compute the execution & symbol context
A
https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/150718
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Jonas Devlieghere
Date: 2025-07-25T18:03:09-07:00
New Revision: e76780b9da76295f88cb24817e9384b88e6416dc
URL:
https://github.com/llvm/llvm-project/commit/e76780b9da76295f88cb24817e9384b88e6416dc
DIFF:
https://github.com/llvm/llvm-project/commit/e76780b9da76295f88cb24817e9384b88e6416dc.d
https://github.com/jimingham approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/150718
___
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/150718
Protected m_selected_frame_idx using the StackFrameList mutex. All other
readers and writes already take the m_list_mutex so we can use that to protect
concurrent access.
>From 0c77d94246d94004e73d7e097a3
igorkudrin wrote:
> This makes sense, but I wouldn't want people to start using
> `@remove_test_categories` randomly. Could you make it so that the removal
> logic is internal to the magic test multiplier? The code is already dealing
> with categories explicitly, so I think that you could just
https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/150714
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Jonas Devlieghere
Date: 2025-07-25T15:55:21-07:00
New Revision: cf6a4bbc42c7e54bf6e251206134b207e757b604
URL:
https://github.com/llvm/llvm-project/commit/cf6a4bbc42c7e54bf6e251206134b207e757b604
DIFF:
https://github.com/llvm/llvm-project/commit/cf6a4bbc42c7e54bf6e251206134b207e757b604.d
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/150579
>From f687e98f005544a4a9c7dad38579f5f91573a6ed Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Thu, 24 Jul 2025 23:46:37 -0700
Subject: [PATCH] [lldb][test] Fix running TestWithLimitDebugInfo.py on Windows
@@ -323,6 +323,14 @@ else()
set(LLDB_CAN_USE_DEBUGSERVER OFF)
endif()
+if (NOT DEFINED LLDB_CAN_USE_LLDB_RPC_SERVER)
+ set(LLDB_CAN_USE_LLDB_RPC_SERVER OFF)
+endif()
+
+if (NOT DEFINED LLDB_BUILD_LLDBRPC)
vvereschaka wrote:
Probably you just forgot to re
https://github.com/chelcassanova updated
https://github.com/llvm/llvm-project/pull/150699
>From e2aeab7dfb6a7db3f43a9a714d3b00de36ecf5f3 Mon Sep 17 00:00:00 2001
From: Chelsea Cassanova
Date: Fri, 25 Jul 2025 13:43:43 -0700
Subject: [PATCH] [lldb][rpc] Disable building lldb-rpc-gen tool
Disabl
https://github.com/mstorsjo approved this pull request.
Not sure if this is the best/nicest fix, but it works for unbreaking my builds,
so thanks!
https://github.com/llvm/llvm-project/pull/150699
___
lldb-commits mailing list
lldb-commits@lists.llvm.o
https://github.com/chelcassanova updated
https://github.com/llvm/llvm-project/pull/150699
>From 9890570dd8819bdc3e745b045c725d335a304c9a Mon Sep 17 00:00:00 2001
From: Chelsea Cassanova
Date: Fri, 25 Jul 2025 13:43:43 -0700
Subject: [PATCH] [lldb][rpc] Disable building lldb-rpc-gen tool
Disabl
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Chelsea Cassanova (chelcassanova)
Changes
Disabling the lldb-rpc-gen tool while issues with certain builds are solved:
https://github.com/llvm/llvm-project/pull/148996
---
Full diff: https://github.com/llvm/llvm-project/pull/150699.diff
https://github.com/chelcassanova created
https://github.com/llvm/llvm-project/pull/150699
Disabling the lldb-rpc-gen tool while issues with certain builds are solved:
https://github.com/llvm/llvm-project/pull/148996
>From cd91a8c70687e28fe1089e24cbcd45d3c44d0133 Mon Sep 17 00:00:00 2001
From:
vvereschaka wrote:
Thank you @mstorsjo ,
>This is fairly easy to reproduce on Linux, if you e.g. on x86_64 linux have
>aarch64 cross compilers available (on Debian/Ubuntu available by installing
>g++-aarch64-linux-gnu):
I suppose, the LLVM_HOST_TRIPLE option causes that problem with RPC gen,
mstorsjo wrote:
Also, another less fatal annoyance: If compiling LLDB with GCC, this now
produces warnings like these:
```
[1/78] Processing file
/home/martin/code/llvm-project/lldb/include/lldb/API/SBAddress.h.
warning: unknown warning option '-Wno-class-memaccess'; did you mean
'-Wno-class-v
https://github.com/chelcassanova updated
https://github.com/llvm/llvm-project/pull/147655
>From fd971a1109662f763b2c273fb39d2ef431afbe60 Mon Sep 17 00:00:00 2001
From: Chelsea Cassanova
Date: Thu, 24 Jul 2025 14:05:55 -0700
Subject: [PATCH 1/4] [lldb][rpc] Add RPC client library tests
Adds she
santhoshe447 wrote:
> This patch still only recognizes the `xqci` from the ELF file and adds it to
> the disassembly flags (v. ObjectFileELF::GetSectionHeaderInfo,
> ObjectFileELF::ParseRISCVAttributes).
>
> Is this the only attribute that can be set via this mechanism? is it possible
> for o
https://github.com/JDevlieghere requested changes to this pull request.
The [LLVM Developer
Policy](https://llvm.org/docs/DeveloperPolicy.html#ai-generated-contributions)
states:
> While the LLVM project has a liberal policy on AI tool use, contributors are
> considered responsible for their
JDevlieghere wrote:
> @JDevlieghere do you have a WIP tree they can use that has more changes?
Not currently no, but it's only one or two patches more patches before we have
parity with the original PR. I just need to decide how to split them up once
this PR lands.
As much as I enjoy the disc
@@ -134,7 +134,9 @@ bool TypeQuery::ContextMatches(
if (ctx == ctx_end)
return false; // Pattern too long.
-if (ctx->kind == CompilerContextKind::Namespace && ctx->name.IsEmpty()) {
+if ((ctx->kind & CompilerContextKind::Namespace) ==
Nerixyz
@@ -2471,6 +2471,47 @@ bool SymbolFileDWARF::ResolveFunction(const DWARFDIE
&orig_die,
return false;
}
+llvm::Error
+SymbolFileDWARF::FindAndResolveFunction(SymbolContextList &sc_list,
+llvm::StringRef lookup_name) {
+ std::lock_guar
@@ -771,6 +774,63 @@ class LoadAddressResolver {
lldb::addr_t m_best_internal_load_address = LLDB_INVALID_ADDRESS;
};
+/// Returns address of the function referred to by the special function call
+/// label \c label.
+///
+/// \param[in] label Function call label encoding th
@@ -96,6 +96,31 @@ class Expression {
///invalid.
};
+/// Holds parsed information about a function call label that
+/// LLDB attaches as an AsmLabel to function AST nodes it parses
+/// from debug-info.
+///
+/// The format being:
+///
+///
@@ -96,6 +96,31 @@ class Expression {
///invalid.
};
+/// Holds parsed information about a function call label that
+/// LLDB attaches as an AsmLabel to function AST nodes it parses
+/// from debug-info.
+///
+/// The format being:
+///
+///
Author: nerix
Date: 2025-07-25T17:01:35+01:00
New Revision: 7b42e7c98e13bd9f50db754346de946b3a6e1bbe
URL:
https://github.com/llvm/llvm-project/commit/7b42e7c98e13bd9f50db754346de946b3a6e1bbe
DIFF:
https://github.com/llvm/llvm-project/commit/7b42e7c98e13bd9f50db754346de946b3a6e1bbe.diff
LOG: [L
https://github.com/Michael137 closed
https://github.com/llvm/llvm-project/pull/150318
___
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/150318
___
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/150318
>From 87f45bf97c50a7478fded9702972a83f667c1f68 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Wed, 23 Jul 2025 22:31:28 +0200
Subject: [PATCH 1/2] [LLDB] Add formatters for MSVC STL std::string_view and
friends
Author: David Spickett
Date: 2025-07-25T14:53:28Z
New Revision: 6adbbcc7dbcf4ee65c74d396f555f3e057271d9b
URL:
https://github.com/llvm/llvm-project/commit/6adbbcc7dbcf4ee65c74d396f555f3e057271d9b
DIFF:
https://github.com/llvm/llvm-project/commit/6adbbcc7dbcf4ee65c74d396f555f3e057271d9b.diff
LOG
kuilpd wrote:
> > single interface to traverse the AST tree:
>
> That's the part that would change in this setup. Instead of one API, we'd
> have two: `EvaluateValueNode()` and `EvaluateScalarNode()`, and we'd have two
> node hierarchies: ValueNode and ScalarNode. MemberOfNode would be a Value
@@ -0,0 +1,127 @@
+//===--===//
DavidSpickett wrote:
Cool.
https://github.com/llvm/llvm-project/pull/150143
___
lldb-commits mailing list
lldb-commits
@@ -0,0 +1,127 @@
+//===--===//
+//
+// 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
DavidSpickett wrote:
> I'm personally skeptical of this part. LLDB's command line driver is very
> small and doesn't do much. You absolutely could turn that into a DAP client,
> but you wouldn't get much in return. Most of the "TUI" parts of LLDB are
> tightly coupled with the core of the libr
@@ -20,212 +18,342 @@ using namespace testing;
namespace {
-class MockSyncService : public AdbClient::SyncService {
+class MockConnection : public Connection {
labath wrote:
Is this used anywhere? If it is, it may be better to just use a real connection
ins
@@ -0,0 +1,46 @@
+//===-- AdbClientUtils.h
--===//
+//
+// 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
@@ -220,6 +220,12 @@ ConnectionStatus
ConnectionFileDescriptor::Disconnect(Status *error_ptr) {
// Prevents reads and writes during shutdown.
m_shutting_down = true;
+ if (!m_io_sp) {
labath wrote:
Is this still needed? I mean, it sort of makes sense, b
@@ -8,98 +8,45 @@
#include "AdbClient.h"
-#include "llvm/ADT/STLExtras.h"
-#include "llvm/ADT/SmallVector.h"
-#include "llvm/ADT/StringRef.h"
-#include "llvm/Support/FileUtilities.h"
-
-#include "lldb/Host/ConnectionFileDescriptor.h"
-#include "lldb/Host/FileSystem.h"
-#inclu
@@ -32,50 +34,14 @@ class AdbClient {
using DeviceIDList = std::list;
- class SyncService {
-friend class AdbClient;
-
- public:
-virtual ~SyncService();
-
-virtual Status PullFile(const FileSpec &remote_file,
-const FileSpec &local
@@ -418,13 +436,68 @@ bool PlatformAndroid::GetRemoteOSVersion() {
return !m_os_version.empty();
}
+uint32_t PlatformAndroid::FindProcesses(
+const ProcessInstanceInfoMatch &match_info,
+ProcessInstanceInfoList &process_infos) {
+ Status error;
+ AdbClientUP adb(Ge
@@ -418,13 +436,68 @@ bool PlatformAndroid::GetRemoteOSVersion() {
return !m_os_version.empty();
}
+uint32_t PlatformAndroid::FindProcesses(
labath wrote:
How does this relate to the rest of the patch?
https://github.com/llvm/llvm-project/pull/145382
_
@@ -445,11 +518,9 @@
PlatformAndroid::GetLibdlFunctionDeclarations(lldb_private::Process *process) {
}
PlatformAndroid::AdbClientUP PlatformAndroid::GetAdbClient(Status &error) {
- AdbClientUP adb(std::make_unique(m_device_id));
- if (adb)
-error.Clear();
- else
-e
@@ -108,62 +55,73 @@ Status AdbClient::CreateByDeviceID(const std::string
&device_id,
"Expected a single connected device, got instead %zu - try "
"setting 'ANDROID_SERIAL'",
connected_devices.size());
-adb.SetDeviceID(connected_devices.front(
https://github.com/labath 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
https://github.com/labath commented:
I like what you've done, though it makes it a bit difficult to review. In the
future, if you find yourself moving lot of code around, try to separate that
from the functional changes into a PR of its own. That makes things flow a lot
easier.
In this case,
DavidSpickett wrote:
> Hence why I think the "user" approach is the most promising, generally
> speaking.
Agreed. If I want to debug qemu-user I treat it like any other program, if I
want the simulated process I connect to the internal stub. Some will want
integrated solutions but that can co
mh4ck-Thales wrote:
I tested this patch and while basic debugging works, some features that were
available in #77949 are not working anymore (retrieval of variable values,
disassembly of the Wasm bytecode...). I'm not sure if it's a bug or if it's
because the #77949 patch has been split into i
mh4ck-Thales wrote:
> I'd be happy to keep chatting about this if you're interested in exploring
> that path further, now or in the future. I also don't want to necessarily
> push you towards the GDB remote protocol. For languages like C++, Rust,
> Swift, or really anything targeting LLVM/supp
DavidSpickett wrote:
> It also adds tests for both plugins. They are shell tests, because API tests
> currently only test with DWARF and after
> https://github.com/llvm/llvm-project/pull/149305 they'd only test with one
> plugin. They're not as exhaustive as the API tests - their goal is to sh
@@ -0,0 +1,127 @@
+//===--===//
+//
+// 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,162 @@
+//===-- AdbClientUtils.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,162 @@
+//===-- AdbClientUtils.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
https://github.com/labath commented:
This makes sense, but I wouldn't want people to start using
`@remove_test_categories` randomly. Could you make it so that the removal logic
is internal to the magic test multiplier? The code is already dealing with
categories explicitly, so I think that you
@@ -1799,6 +1799,7 @@ def no_reason(_):
for cat in categories:
@decorators.add_test_categories([cat])
+@decorators.remove_test_categories(categories)
labath wrote:
(Also, the decorators are applied from
@@ -1799,6 +1799,7 @@ def no_reason(_):
for cat in categories:
@decorators.add_test_categories([cat])
+@decorators.remove_test_categories(categories)
labath wrote:
The loop creates a new function every i
@@ -771,6 +774,63 @@ class LoadAddressResolver {
lldb::addr_t m_best_internal_load_address = LLDB_INVALID_ADDRESS;
};
+/// Returns address of the function referred to by the special function call
+/// label \c label.
+///
+/// \param[in] label Function call label encoding th
@@ -2471,6 +2471,47 @@ bool SymbolFileDWARF::ResolveFunction(const DWARFDIE
&orig_die,
return false;
}
+llvm::Error
+SymbolFileDWARF::FindAndResolveFunction(SymbolContextList &sc_list,
+llvm::StringRef lookup_name) {
+ std::lock_guar
DavidSpickett wrote:
Your idea sounds fine, no idea if any of these are load bearing but test suites
are the only way to find out. If Mac is fine go ahead and land this, the
AArch64 Linux bot has top byte ignore and pointer authentication available.
https://github.com/llvm/llvm-project/pull/15
llvmbot wrote:
/pull-request llvm/llvm-project#150600
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
@@ -96,6 +96,31 @@ class Expression {
///invalid.
};
+/// Holds parsed information about a function call label that
+/// LLDB attaches as an AsmLabel to function AST nodes it parses
+/// from debug-info.
+///
+/// The format being:
+///
+///
labath wrote:
Okay, here goes nothing.
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
labath wrote:
/cherry-pick f5c676d6d95dc63b8dcb43dd2e4dfc913a9c5a50
33396d71e9aef624670380e11348a11b8ff74246
https://github.com/llvm/llvm-project/pull/147887
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mail
https://github.com/labath milestoned
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
labath wrote:
I don't think that `m_object_name` is what you're looking for. It's supposed to
be used for disambiguation when a single physical file contains multiple
logical object files, such as with BSD archives. It being empty for "normal"
files is kind of expected:
```
ConstString m_obj
@@ -247,6 +248,28 @@ uint32_t File::GetPermissions(Status &error) const {
return file_stats.st_mode & (S_IRWXU | S_IRWXG | S_IRWXO);
}
+NativeFile::NativeFile()
+: m_descriptor(kInvalidDescriptor), m_stream(kInvalidStream) {}
+
+NativeFile::NativeFile(FILE *fh, bool tran
DavidSpickett wrote:
Same issue reported in https://github.com/llvm/llvm-project/issues/150454.
https://github.com/llvm/llvm-project/pull/148996
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/l
@@ -1978,7 +1978,12 @@ llvm::Expected DWARFExpression::Evaluate(
// grows to the nearest host integer type.
llvm::APInt fail_value(1, 0, false);
llvm::APInt ap_int = scalar.UInt128(fail_value);
-assert(ap_int.getBitWidth() >= bit_
https://github.com/labath edited
https://github.com/llvm/llvm-project/pull/150149
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/labath commented:
I'm not sure that what clang is doing is completely compliant. According to the
standard, DWARF expression values """can represent a value of any supported
base type of the target machine. Instead of a base type, elements can have a
generic type, which is a
@@ -134,7 +134,9 @@ bool TypeQuery::ContextMatches(
if (ctx == ctx_end)
return false; // Pattern too long.
-if (ctx->kind == CompilerContextKind::Namespace && ctx->name.IsEmpty()) {
+if ((ctx->kind & CompilerContextKind::Namespace) ==
labath
https://github.com/Michael137 approved this pull request.
LGTM (just left comment re. null summary)
https://github.com/llvm/llvm-project/pull/150318
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listin
@@ -78,14 +78,12 @@ def cleanup():
"u32_string", type="std::u32string_view", summary='U"🍄🍅🍆🍌"'
)
self.expect_var_path("u32_empty", type="std::u32string_view",
summary='U""')
-self.expect_var_path(
-"oops", type="std::string_view"
llvmbot wrote:
/pull-request llvm/llvm-project#150591
https://github.com/llvm/llvm-project/pull/150398
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: David Spickett
Date: 2025-07-25T08:41:16Z
New Revision: c63c2f4972f63cd19352719c966659bb80cec450
URL:
https://github.com/llvm/llvm-project/commit/c63c2f4972f63cd19352719c966659bb80cec450
DIFF:
https://github.com/llvm/llvm-project/commit/c63c2f4972f63cd19352719c966659bb80cec450.diff
LOG
https://github.com/DavidSpickett milestoned
https://github.com/llvm/llvm-project/pull/150398
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
DavidSpickett wrote:
/cherry-pick 1a32bcb4379fb90d2b764ac33b917de1431c6b16
https://github.com/llvm/llvm-project/pull/150398
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/DavidSpickett edited
https://github.com/llvm/llvm-project/pull/150579
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -1799,6 +1799,7 @@ def no_reason(_):
for cat in categories:
@decorators.add_test_categories([cat])
+@decorators.remove_test_categories(categories)
DavidSpickett wrote:
I don't understand how this loop
https://github.com/DavidSpickett commented:
Agree with the intent, very confused by the implementation.
https://github.com/llvm/llvm-project/pull/150579
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/li
@@ -2471,6 +2471,47 @@ bool SymbolFileDWARF::ResolveFunction(const DWARFDIE
&orig_die,
return false;
}
+llvm::Error
+SymbolFileDWARF::FindAndResolveFunction(SymbolContextList &sc_list,
+llvm::StringRef lookup_name) {
+ std::lock_guar
@@ -771,6 +774,63 @@ class LoadAddressResolver {
lldb::addr_t m_best_internal_load_address = LLDB_INVALID_ADDRESS;
};
+/// Returns address of the function referred to by the special function call
+/// label \c label.
+///
+/// \param[in] label Function call label encoding th
@@ -96,6 +96,31 @@ class Expression {
///invalid.
};
+/// Holds parsed information about a function call label that
+/// LLDB attaches as an AsmLabel to function AST nodes it parses
+/// from debug-info.
+///
+/// The format being:
+///
+///
cjdb wrote:
@ldionne Would you mind reviewing this again, please?
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
87 matches
Mail list logo
