llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Brad Smith (brad0)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/124383.diff
1 Files Affected:
- (modified) lldb/source/Host/posix/HostInfoPosix.cpp (+4)
``diff
diff --git a/lldb/source/Host/posix/HostInfoP
brad0 wrote:
>From the look of the rest of the codebase I should have included this header
>when utilizing __ANDROID_API__.
https://github.com/llvm/llvm-project/pull/124383
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.o
https://github.com/brad0 created
https://github.com/llvm/llvm-project/pull/124383
None
>From b0580b8b0f1f50e5fa10d2b872c79b4942faf093 Mon Sep 17 00:00:00 2001
From: Brad Smith
Date: Fri, 24 Jan 2025 21:38:07 -0500
Subject: [PATCH] [lldb] Include api-level.h header for Android
---
lldb/source
SuibianP wrote:
I [enabled `runInTerminal` tests for
Windows](https://github.com/llvm/llvm-project/pull/121269/files#diff-38cf10e0a83515e5c6acf5449a3f5de1d63f116d932a32ba169b746826ead1d4)
(will fix line 93 later) except for the 4 launcher tests that requires
`os.mkfifo` (https://github.com/pyt
https://github.com/Jlalond closed
https://github.com/llvm/llvm-project/pull/124355
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Jacob Lalonde
Date: 2025-01-24T14:59:56-08:00
New Revision: e2005d1461942539f7533a518aa78017074f6bf9
URL:
https://github.com/llvm/llvm-project/commit/e2005d1461942539f7533a518aa78017074f6bf9
DIFF:
https://github.com/llvm/llvm-project/commit/e2005d1461942539f7533a518aa78017074f6bf9.diff
https://github.com/JDevlieghere approved this pull request.
https://github.com/llvm/llvm-project/pull/124355
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Jlalond edited
https://github.com/llvm/llvm-project/pull/124355
___
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: Jacob Lalonde (Jlalond)
Changes
In my last attempt at this (#123873), I didn't realize we needed semi
colons! Also fixed the bug that the feature summary didn't have a type defined.
CC @JDevlieghere hope you get a laugh at needing to rever
https://github.com/Jlalond created
https://github.com/llvm/llvm-project/pull/124355
In my last attempt at this (#123873), I didn't realize we needed semi colons!
Also fixed the bug that the feature summary didn't have a type defined.
CC @JDevlieghere hope you get a laugh at needing to revert d
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/124279
>From 23c7f4a3e067739a050964b3f1c2140787b0c31f Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Fri, 24 Jan 2025 13:33:07 +
Subject: [PATCH 1/4] [lldb][TypeSystem] Ensure that ParmVarDecls have the
corr
jimingham wrote:
I think that argument has some force for synthetic child providers, but less so
for summaries. I'd like to see the size of a std::vector regardless of whether
I'm holding it as a *, **, etc.
https://github.com/llvm/llvm-project/pull/124048
Author: Dave Lee
Date: 2025-01-24T10:02:15-08:00
New Revision: 7293455cf292cfaa263ea04fc1bc2aee4ceab6a6
URL:
https://github.com/llvm/llvm-project/commit/7293455cf292cfaa263ea04fc1bc2aee4ceab6a6
DIFF:
https://github.com/llvm/llvm-project/commit/7293455cf292cfaa263ea04fc1bc2aee4ceab6a6.diff
LOG:
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-remote-linux-win`
running on `as-builder-10` while building `lldb` at step 17
"test-check-lldb-api".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/197/builds/
Here is the relevant piece of
emrekultursay wrote:
On the Android Studio side, we don't run tests on old API levels. We only run
automated on latest API levels (and some best-effort manual tests on recent-ish
API levels). Different features in Android Studio have different min-API
requirements. To me, it seems OK to add "A
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-remote-linux-ubuntu`
running on `as-builder-9` while building `lldb` at step 16
"test-check-lldb-api".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/195/builds/3971
Here is the relevant piece
enh-google wrote:
> > that's especially weird because execve() doesn't use $PATH ... it's the
> > members of the exec family that have a 'p' in the name that do.
>
> It's been a long time, but I'm pretty sure this was due to a test which ran
> something with an empty environment (some of our t
https://github.com/kastiglione closed
https://github.com/llvm/llvm-project/pull/123981
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Brad Smith
Date: 2025-01-24T11:33:05-05:00
New Revision: cccb55491223cd410cb2f83973377dd75757cb60
URL:
https://github.com/llvm/llvm-project/commit/cccb55491223cd410cb2f83973377dd75757cb60
DIFF:
https://github.com/llvm/llvm-project/commit/cccb55491223cd410cb2f83973377dd75757cb60.diff
LO
https://github.com/brad0 closed https://github.com/llvm/llvm-project/pull/124257
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/124279
>From 23c7f4a3e067739a050964b3f1c2140787b0c31f Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Fri, 24 Jan 2025 13:33:07 +
Subject: [PATCH 1/3] [lldb][TypeSystem] Ensure that ParmVarDecls have the
corr
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/124279
>From 23c7f4a3e067739a050964b3f1c2140787b0c31f Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Fri, 24 Jan 2025 13:33:07 +
Subject: [PATCH 1/2] [lldb][TypeSystem] Ensure that ParmVarDecls have the
corr
https://github.com/DavidSpickett edited
https://github.com/llvm/llvm-project/pull/124295
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/DavidSpickett updated
https://github.com/llvm/llvm-project/pull/124295
>From 951a38910e49f3e93dc6c9a084e955ab01ad4c49 Mon Sep 17 00:00:00 2001
From: David Spickett
Date: Fri, 9 Aug 2024 11:56:29 +0100
Subject: [PATCH 1/6] [lldb][AArch64] Add Guarded Control Stack registers
T
DavidSpickett wrote:
This is the last piece of functionality for GCS.
Remaining is the documentation
(https://github.com/llvm/llvm-project/pull/117860) and a release note that I'll
push directly if the 20 branch hasn't happened yet by that time.
https://github.com/llvm/llvm-project/pull/12429
DavidSpickett wrote:
All commits before the one named the same as this PR are from
https://github.com/llvm/llvm-project/pull/124293. I will handle the rebasing
and conflicts as that gets landed.
https://github.com/llvm/llvm-project/pull/124295
___
ll
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: David Spickett (DavidSpickett)
Changes
The features and locked registers hold the same bits, the latter
is a lock for the former. Tested with core files and live processes.
I thought about setting a non-zero lock register in the core file,
https://github.com/DavidSpickett created
https://github.com/llvm/llvm-project/pull/124295
The features and locked registers hold the same bits, the latter
is a lock for the former. Tested with core files and live processes.
I thought about setting a non-zero lock register in the core file,
howe
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/124279
___
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/124279
___
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/124293
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Michael137 wrote:
Hmm one important difference here is that we would now not attach a name to the
parameters that we create for free functions (we already don't do it for
methods). I don't think having a name on the parameter is important for
anything other than diagnostics of the expression e
DavidSpickett wrote:
Only the latest commit is new, the rest is from
https://github.com/llvm/llvm-project/pull/123918. I will rebase and fix
conflicts as and when these get landed.
https://github.com/llvm/llvm-project/pull/124293
___
lldb-commits mai
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: David Spickett (DavidSpickett)
Changes
This allows you to read the same registers as you would for a live process.
As the content of proc/pid/smaps is not included in the core file,
we don't get the "ss" marker. The GCS region is stil in th
https://github.com/DavidSpickett created
https://github.com/llvm/llvm-project/pull/124293
This allows you to read the same registers as you would for a live process.
As the content of proc/pid/smaps is not included in the core file,
we don't get the "ss" marker. The GCS region is stil in the li
https://github.com/jmorse created
https://github.com/llvm/llvm-project/pull/124287
As part of the "RemoveDIs" work to eliminate debug intrinsics, we're replacing
methods that use Instruction*'s as positions with iterators. A number of these
(such as getFirstNonPHIOrDbg) are sufficiently infreq
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 c546b5317c518987a5f45dd4c4d25321a955c758
3d2aa2734d6cb49c43565e3ac8584ba8130fe302 --e
llvmbot wrote:
@llvm/pr-subscribers-backend-aarch64
Author: Jeremy Morse (jmorse)
Changes
As part of the "RemoveDIs" work to eliminate debug intrinsics, we're replacing
methods that use Instruction*'s as positions with iterators. A number of these
(such as getFirstNonPHIOrDbg) are suffic
llvmbot wrote:
@llvm/pr-subscribers-backend-nvptx
Author: Jeremy Morse (jmorse)
Changes
As part of the "RemoveDIs" work to eliminate debug intrinsics, we're replacing
methods that use Instruction*'s as positions with iterators. A number of these
(such as getFirstNonPHIOrDbg) are sufficie
llvmbot wrote:
@llvm/pr-subscribers-llvm-transforms
@llvm/pr-subscribers-llvm-ir
Author: Jeremy Morse (jmorse)
Changes
As part of the "RemoveDIs" work to eliminate debug intrinsics, we're replacing
methods that use Instruction*'s as positions with iterators. A number of these
(such as ge
https://github.com/Michael137 created
https://github.com/llvm/llvm-project/pull/124279
While sifting through this part of the code I noticed that when we parse C++
methods, `DWARFASTParserClang` creates two sets of `ParmVarDecls`, one in
`ParseChildParameters` and once in `AddMethodToCXXRecord
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Michael Buch (Michael137)
Changes
While sifting through this part of the code I noticed that when we parse C++
methods, `DWARFASTParserClang` creates two sets of `ParmVarDecls`, one in
`ParseChildParameters` and once in `AddMethodToCXXReco
@@ -83,3 +83,278 @@ def test_gcs_fault(self):
"stop reason = signal SIGSEGV: control protection fault",
],
)
+
+def check_gcs_registers(
+self,
+expected_gcs_features_enabled=None,
+expected_gcs_features_locked=Non
@@ -87,6 +150,18 @@ bool ABISysV_arm64::PrepareTrivialCall(Thread &thread,
addr_t sp,
if (args.size() > 8)
return false;
+ // Do this first, as it's got the most chance of failing (though still very
+ // low).
+ if (GetProcessSP()->GetTarget().GetArchitecture().GetTr
@@ -60,6 +60,69 @@ ABISysV_arm64::CreateInstance(lldb::ProcessSP process_sp,
const ArchSpec &arch)
return ABISP();
}
+static Status PushToLinuxGuardedControlStack(addr_t return_addr,
+ RegisterContext *reg_ctx,
+
DavidSpickett wrote:
This conflicts a lot with main but I'm going to deal with that after approval.
https://github.com/llvm/llvm-project/pull/123918
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listin
@@ -103,6 +156,9 @@ bool ABISysV_arm64::PrepareTrivialCall(Thread &thread,
addr_t sp,
return_addr))
return false;
+ if (GetProcessSP()->GetTarget().GetArchitecture().GetTriple().isOSLinux())
+PushToLinuxGuardedControlStack(return_addr, reg_ctx, thread);
---
https://github.com/DavidSpickett edited
https://github.com/llvm/llvm-project/pull/123918
___
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/123918
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/DavidSpickett updated
https://github.com/llvm/llvm-project/pull/123918
>From 951a38910e49f3e93dc6c9a084e955ab01ad4c49 Mon Sep 17 00:00:00 2001
From: David Spickett
Date: Fri, 9 Aug 2024 11:56:29 +0100
Subject: [PATCH 1/4] [lldb][AArch64] Add Guarded Control Stack registers
T
https://github.com/enh-google approved this pull request.
https://github.com/llvm/llvm-project/pull/124257
___
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/123720
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: David Spickett
Date: 2025-01-24T13:42:06Z
New Revision: 02c6002d1cd2dabe4b98368f91e7b4395e5ab11d
URL:
https://github.com/llvm/llvm-project/commit/02c6002d1cd2dabe4b98368f91e7b4395e5ab11d
DIFF:
https://github.com/llvm/llvm-project/commit/02c6002d1cd2dabe4b98368f91e7b4395e5ab11d.diff
LOG
@@ -71,12 +74,14 @@ class FifoFileIO {
/// \return
/// An \a llvm::Error object indicating whether the data was consumed by
/// a reader or not.
- llvm::Error SendJSON(
- const llvm::json::Value &json,
- std::chrono::milliseconds timeout = std::chrono::
@@ -21,21 +23,22 @@ namespace lldb_dap {
/// The file is destroyed when the destructor is invoked.
struct FifoFile {
FifoFile(llvm::StringRef path);
+ FifoFile(llvm::StringRef path, FILE *f);
+ // FifoFile(llvm::StringRef path, FILE *f);
+ FifoFile(FifoFile &&other);
+
+
@@ -2,8 +2,8 @@
#include
#include
-#ifndef HWCAP2_GCS
-#define HWCAP2_GCS (1UL << 63)
+#ifndef HWCAP_GCS
+#define HWCAP_GCS (1UL << 32)
DavidSpickett wrote:
Mark Brown confirmed that the documentation is incorrect. It is in HWCAP as the
code shows.
https:
labath wrote:
I ran this on an arm mac, and also on x86-via-rosetta mac (which isn't quite
the same as native, but it's the best I have). I did find one problem, which is
that the packet forwarder misinterprets a response to the `x` packet which
begins with an `O` as an "output" packet. I gues
https://github.com/SuibianP updated
https://github.com/llvm/llvm-project/pull/121269
>From dc866c2d106292b7fe49f8c1ac45dbd3905b81d6 Mon Sep 17 00:00:00 2001
From: Hu Jialun
Date: Sat, 28 Dec 2024 22:39:33 +0800
Subject: [PATCH] [lldb-dap] Implement runInTerminal for Windows
Currently, the name
@@ -158,13 +164,24 @@ std::string
RunInTerminalDebugAdapterCommChannel::GetLauncherError() {
}
Expected> CreateRunInTerminalCommFile() {
+ int comm_fd;
SmallString<256> comm_file;
- if (std::error_code EC = sys::fs::getPotentiallyUniqueTempFileName(
- "lldb-dap-
@@ -111,8 +111,10 @@ Error
RunInTerminalLauncherCommChannel::WaitUntilDebugAdaptorAttaches(
return message.takeError();
}
-Error RunInTerminalLauncherCommChannel::NotifyPid() {
- return m_io.SendJSON(RunInTerminalMessagePid(getpid()).ToJSON());
+Error RunInTerminalLaunch
@@ -71,12 +74,14 @@ class FifoFileIO {
/// \return
/// An \a llvm::Error object indicating whether the data was consumed by
/// a reader or not.
- llvm::Error SendJSON(
- const llvm::json::Value &json,
- std::chrono::milliseconds timeout = std::chrono::
labath wrote:
Thank you both. The cases where I'm creating a function with a single range are
all in non-DWARF plugins, and the range is the only one we have available.
Breakpad definitely doesn't support multiple function ranges. I'm not sure
about PDB, but I didn't find anything obvious ther
https://github.com/labath closed
https://github.com/llvm/llvm-project/pull/122440
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Pavel Labath
Date: 2025-01-24T12:50:06+01:00
New Revision: 57b48987f6c21e369e7bb1626dc79ca74aa34fdb
URL:
https://github.com/llvm/llvm-project/commit/57b48987f6c21e369e7bb1626dc79ca74aa34fdb
DIFF:
https://github.com/llvm/llvm-project/commit/57b48987f6c21e369e7bb1626dc79ca74aa34fdb.diff
https://github.com/brad0 created
https://github.com/llvm/llvm-project/pull/124257
This was for the wrapper function that was in
source/Host/android/LibcGlue.cpp. Android added
support 10+ years ago.
>From ed441c18d824e25a184f348a0dba7019cfb01b6f Mon Sep 17 00:00:00 2001
From: Brad Smith
Date:
https://github.com/labath approved this pull request.
https://github.com/llvm/llvm-project/pull/124257
___
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: Brad Smith (brad0)
Changes
This was for the wrapper function that was in
source/Host/android/LibcGlue.cpp. Android added
support 10+ years ago.
---
Full diff: https://github.com/llvm/llvm-project/pull/124257.diff
1 Files Affected:
- (mod
@@ -0,0 +1,156 @@
+//===-- DILLexer.h --*- C++
-*-===//
+//
+// 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,156 @@
+//===-- DILLexer.h --*- C++
-*-===//
+//
+// 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
labath wrote:
> @labath What do you think? The solution above will still use the formatters
> for `T` when `T**` is printed.
Before I answer that, I want to go back to the question of dereferencing. While
I don't think that skipping of arbitrary numbers of points is *wrong* (it's
consistent a
https://github.com/DavidSpickett updated
https://github.com/llvm/llvm-project/pull/123720
>From 951a38910e49f3e93dc6c9a084e955ab01ad4c49 Mon Sep 17 00:00:00 2001
From: David Spickett
Date: Fri, 9 Aug 2024 11:56:29 +0100
Subject: [PATCH 1/3] [lldb][AArch64] Add Guarded Control Stack registers
T
https://github.com/labath updated
https://github.com/llvm/llvm-project/pull/123340
>From 2d8987fbffa462c671f0e8cc40accc6ff63aa625 Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Fri, 17 Jan 2025 12:36:36 +0100
Subject: [PATCH] [lldb] Add SymbolContext::GetFunctionOrSymbolAddress
Many uses of
https://github.com/labath approved this pull request.
https://github.com/llvm/llvm-project/pull/122783
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -370,6 +370,31 @@ bool SymbolContext::GetAddressRange(uint32_t scope,
uint32_t range_idx,
return false;
}
+Address SymbolContext::GetAddress(uint32_t scope,
+ bool use_inline_block_range) const {
+ if ((scope & eSymbolContextLineEntry) &
https://github.com/labath edited
https://github.com/llvm/llvm-project/pull/123340
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/labath edited
https://github.com/llvm/llvm-project/pull/123340
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -83,3 +83,137 @@ def test_gcs_fault(self):
"stop reason = signal SIGSEGV: control protection fault",
],
)
+
+@skipUnlessArch("aarch64")
+@skipUnlessPlatform(["linux"])
+def test_gcs_registers(self):
+if not self.isAArch
https://github.com/DavidSpickett updated
https://github.com/llvm/llvm-project/pull/123720
>From 951a38910e49f3e93dc6c9a084e955ab01ad4c49 Mon Sep 17 00:00:00 2001
From: David Spickett
Date: Fri, 9 Aug 2024 11:56:29 +0100
Subject: [PATCH 1/2] [lldb][AArch64] Add Guarded Control Stack registers
T
@@ -103,6 +156,9 @@ bool ABISysV_arm64::PrepareTrivialCall(Thread &thread,
addr_t sp,
return_addr))
return false;
+ if (GetProcessSP()->GetTarget().GetArchitecture().GetTriple().isOSLinux())
+PushToLinuxGuardedControlStack(return_addr, reg_ctx, thread);
---
@@ -103,6 +156,9 @@ bool ABISysV_arm64::PrepareTrivialCall(Thread &thread,
addr_t sp,
return_addr))
return false;
+ if (GetProcessSP()->GetTarget().GetArchitecture().GetTriple().isOSLinux())
+PushToLinuxGuardedControlStack(return_addr, reg_ctx, thread);
---
@@ -83,3 +83,137 @@ def test_gcs_fault(self):
"stop reason = signal SIGSEGV: control protection fault",
],
)
+
+@skipUnlessArch("aarch64")
+@skipUnlessPlatform(["linux"])
+def test_gcs_registers(self):
+if not self.isAArch
@@ -2,8 +2,8 @@
#include
#include
-#ifndef HWCAP2_GCS
-#define HWCAP2_GCS (1UL << 63)
+#ifndef HWCAP_GCS
+#define HWCAP_GCS (1UL << 32)
DavidSpickett wrote:
Yes that is strange. Initially it was a HWCAP2 value but it was moved for some
reason. I think this
DavidSpickett wrote:
`lldb/test/API/functionalities/postmortem/elf-core/TestLinuxCore.py` -
`test_loongarch64_regs` for example. You should be able to read all those
registers using the aliases as well as the normal names. If you look through
the LoongArch lldb changes you'll probably find the
https://github.com/DavidSpickett approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/122440
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Brad Smith
Date: 2025-01-24T03:19:34-05:00
New Revision: eda16991adeb078647b2d239fcf666ddece5c30a
URL:
https://github.com/llvm/llvm-project/commit/eda16991adeb078647b2d239fcf666ddece5c30a
DIFF:
https://github.com/llvm/llvm-project/commit/eda16991adeb078647b2d239fcf666ddece5c30a.diff
LO
https://github.com/brad0 closed https://github.com/llvm/llvm-project/pull/124187
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/brad0 closed https://github.com/llvm/llvm-project/pull/124182
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Brad Smith
Date: 2025-01-24T03:18:36-05:00
New Revision: a6cfde62bb89e595db2bf7bb8ae810293d8edf26
URL:
https://github.com/llvm/llvm-project/commit/a6cfde62bb89e595db2bf7bb8ae810293d8edf26
DIFF:
https://github.com/llvm/llvm-project/commit/a6cfde62bb89e595db2bf7bb8ae810293d8edf26.diff
LO
https://github.com/labath approved this pull request.
https://github.com/llvm/llvm-project/pull/124187
___
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.
https://github.com/llvm/llvm-project/pull/124182
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
labath wrote:
All of these workarounds are very old. They date back to the time that API
level 21 was brand sparkling new, we were trying to support everything back to
level 8, and NDK headers were missing many important functions. This is why you
can find references to highly questionable pra
https://github.com/Anthony-Eid updated
https://github.com/llvm/llvm-project/pull/124232
>From e741fc75ccb6e2a725b3b26dd4c503cdea6c5fbb Mon Sep 17 00:00:00 2001
From: Anthony Eid
Date: Fri, 24 Jan 2025 00:43:39 -0500
Subject: [PATCH 1/2] Stop using replicated variable ids
---
lldb/tools/lldb-d
92 matches
Mail list logo
