https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/152817
`GetHeapRanges()` could return two overlapping ranges because it did not check
whether `heap_pointer1` lies within the range returned for `heap_pointer2`.
This could result in a test failure in `test_find_ra
igorkudrin wrote:
> Seems like this is [tripping
> up](https://ci.swift.org/view/all/job/llvm.org/view/LLDB/job/lldb-cmake-sanitized/2038/testReport/lldb-unit/Instruction___EmulatorTests_1/16/)
> UBSan:
Thanks for reporting, fixed in 11e1d46
https://github.com/llvm/llvm-project/pull/151460
__
Author: Igor Kudrin
Date: 2025-08-07T13:01:52-07:00
New Revision: 11e1d465860903fd9ead27c0c1e60de4439011db
URL:
https://github.com/llvm/llvm-project/commit/11e1d465860903fd9ead27c0c1e60de4439011db
DIFF:
https://github.com/llvm/llvm-project/commit/11e1d465860903fd9ead27c0c1e60de4439011db.diff
L
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/151460
>From e7ae06b1388e172a83fea0340f81d437b9da3c88 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Wed, 30 Jul 2025 23:28:59 -0700
Subject: [PATCH 1/6] [lldb] Fix auto advance PC in 'EmulateInstructionARM64'
if
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/151803
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/151803
`PlatformList::Create()` added an item in the list even if `Platform::Create()`
returned `nullptr`. Other methods use items of the list without checking, which
can lead to a crash. For example:
```
> lldb
(
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/151635
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
igorkudrin wrote:
Thanks!
> There will be a few registers in each frame to cover the last 1 integer.
I counted `my_ints` itself for this last 1 integer. Yes, there are some
registers stored in the past frames, but there is no point in guessing how many.
https://github.com/llvm/llvm-project/pu
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/151635
>From e6bb5f48978f4eabc9e49176eb3ffd04f2f0e66c Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Thu, 31 Jul 2025 20:39:15 -0700
Subject: [PATCH 1/2] [lldb] Ensure that TestMemoryCache.py reads allocated
memo
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/151635
The test reads 400 bytes of memory above the local variable. If the stack is
shallow, this can reach non-allocated space, resulting in a test failure.
>From e6bb5f48978f4eabc9e49176eb3ffd04f2f0e66c Mon Sep 1
@@ -13,15 +13,124 @@
#include "lldb/Core/Disassembler.h"
#include "lldb/Target/ExecutionContext.h"
#include "lldb/Utility/ArchSpec.h"
+#include "lldb/Utility/RegisterValue.h"
#include "Plugins/Instruction/ARM64/EmulateInstructionARM64.h"
+#include "Plugins/Process/Utility/Re
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/151460
>From e7ae06b1388e172a83fea0340f81d437b9da3c88 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Wed, 30 Jul 2025 23:28:59 -0700
Subject: [PATCH 1/5] [lldb] Fix auto advance PC in 'EmulateInstructionARM64'
if
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/151460
The `EmulateInstructionARM64::EvaluateInstruction()` method used `uint32_t` to
store the PC value, causing addresses greater than 2^32 to be truncated.
As for now, the issue does not affect the mainline beca
https://github.com/igorkudrin closed
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
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/149642
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -1775,16 +1775,20 @@ def no_reason(_):
attrvalue, "__no_debug_info_test__", False
):
# If any debug info categories were explicitly tagged, assume
that list to be
-# authoritative. If none were specified, try with
igorkudrin wrote:
Ping
https://github.com/llvm/llvm-project/pull/149642
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
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/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
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/150579
>From a302c52a378ca5aed5092dbc29ba75447466a66c 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
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/150579
When debug info categories were set for a test method with the
`@add_test_categories` decorator, they were all added to its "categories"
attribute. If some of these categories were not supported,
`LLDBTestR
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/149642
This patch fixes updating persistent variables when memory cannot be allocated
in an inferior process:
```
> lldb -c test.core
(lldb) expr int $i = 5
(lldb) expr $i = 55
(int) $0 = 55
(lldb) expr $i
(int) $i
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/145599
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/145599
>From fac89bb1b51496761b156f22dcff85cbe86bf9d2 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Mon, 23 Jun 2025 23:39:52 -0700
Subject: [PATCH 1/2] [lldb] Fix evaluating expressions without JIT in an
object
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/146016
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
igorkudrin wrote:
> But we do support scalar persistent expression results in core files
> currently:
>
> (lldb) expr int $my_int = 5
(lldb) expr $my_int * 2
(int) $0 = 10
>
> and that should still work after your change. I see no reason why it
> wouldn't, but it would be good to add some use
@@ -321,7 +321,8 @@ IRMemoryMap::Allocation::Allocation(lldb::addr_t
process_alloc,
lldb::addr_t IRMemoryMap::Malloc(size_t size, uint8_t alignment,
uint32_t permissions, AllocationPolicy policy,
- bool zero_mem
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/145599
>From fac89bb1b51496761b156f22dcff85cbe86bf9d2 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Mon, 23 Jun 2025 23:39:52 -0700
Subject: [PATCH 1/2] [lldb] Fix evaluating expressions without JIT in an
object
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/139196
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
igorkudrin wrote:
Ping.
https://github.com/llvm/llvm-project/pull/139196
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/139196
>From 499f723c3f974ff53deb8f354d879e0baaa7a9e8 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Wed, 7 May 2025 19:55:07 -0700
Subject: [PATCH 1/4] [lldb][core] Fix getting summary of a variable pointing
to
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/139196
>From 499f723c3f974ff53deb8f354d879e0baaa7a9e8 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Wed, 7 May 2025 19:55:07 -0700
Subject: [PATCH 1/3] [lldb][core] Fix getting summary of a variable pointing
to
igorkudrin wrote:
Yes, the program file contains the debug information and the read-only section
with the data, so both the core and program files are required. And there are
no core files with the same properties already committed. The program is built
from
@@ -735,14 +735,25 @@ size_t ValueObject::GetPointeeData(DataExtractor &data,
uint32_t item_idx,
case eAddressTypeLoad: {
ExecutionContext exe_ctx(GetExecutionContextRef());
Process *process = exe_ctx.GetProcessPtr();
- if (process) {
+ if (process &&
@@ -735,14 +735,25 @@ size_t ValueObject::GetPointeeData(DataExtractor &data,
uint32_t item_idx,
case eAddressTypeLoad: {
ExecutionContext exe_ctx(GetExecutionContextRef());
Process *process = exe_ctx.GetProcessPtr();
- if (process) {
+ if (process &&
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/139197
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/139197
>From 3faf0c0a4a19d7e1d503c31a684d79295e414be4 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Thu, 8 May 2025 18:37:34 -0700
Subject: [PATCH 1/2] [lldb][NFC] Avoid an assertion failure in dwim-print
In a D
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/139197
In a Debug build on Windows, printing inline diagnostics resulted in an error,
for example:
```
> cd llvm-project\lldb\test\API\functionalities\postmortem\elf-core
> lldb.exe -c altmain.core
> p dummy
LLDB d
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/139196
Motivation example:
```
> lldb -c altmain2.core
...
(lldb) var F
(const char *) F = 0x0804a000 ""
```
The variable `F` points to a read-only memory page not dumped to the core file,
so `Process::ReadMemory(
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/131979
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/131979
An invalid RLE sequence in the received packet could result in an out-of-bounds
reading that could cause a crash.
>From 239aeaa5686350681dc79cad63d5aae5a5f2310a Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Da
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/131736
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/131736
After https://reviews.llvm.org/D116539, when `m_gdb_client_up` in
`PlatformRemoteGDBServer` is not null, the connection to a server is expected
to exist. However, `PlatformRemoteGDBServer::DisconnectRemote()
https://github.com/igorkudrin approved this pull request.
LGTM. Thanks!
https://github.com/llvm/llvm-project/pull/113251
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/igorkudrin edited
https://github.com/llvm/llvm-project/pull/113251
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -6,3 +6,6 @@ include Makefile.rules
# Copy file into the build folder to enable the test to modify it.
main-copy.cpp: main.cpp
cp -f $< $@
+ifneq "$(OS)" "Windows_NT" # chmod is not available on Windows
igorkudrin wrote:
If I understand correctly, w
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/111951
>From e027444340be4020002126da0d2c8a705c2c7e3f Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Thu, 10 Oct 2024 20:27:10 -0700
Subject: [PATCH 1/2] [lldb] Speed up FindInMemory tests
A memory region can be
@@ -6,27 +6,30 @@
UNALIGNED_INSTANCE_PATTERN_HEAP = ALIGNED_INSTANCE_PATTERN_HEAP[1:]
-def GetAlignedRange(test_base):
+def GetAlignedRange(test_base, shrink=False):
frame = test_base.thread.GetSelectedFrame()
ex = frame.EvaluateExpression("aligned_string_ptr")
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/111951
>From e027444340be4020002126da0d2c8a705c2c7e3f Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Thu, 10 Oct 2024 20:27:10 -0700
Subject: [PATCH] [lldb] Speed up FindInMemory tests
A memory region can be rela
https://github.com/igorkudrin edited
https://github.com/llvm/llvm-project/pull/111951
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/111951
A memory region can be relatively large. Searching for a value in the entire
region is time-consuming, especially when running tests against a remote
target, because the memory data is transferred in small c
https://github.com/igorkudrin edited
https://github.com/llvm/llvm-project/pull/111237
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
igorkudrin wrote:
So the test basically shows that it makes sense to set `use-source-cache` to
`false` on Windows, otherwise the source file will be locked for editing.
Windows 11 seems to allow deleting mmaped files, so we need to try opening the
file for writing to re-enable the test. Thanks
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/111237
>From 6756842b1c78ac6f41fa467f112aa7632f260582 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Fri, 4 Oct 2024 23:27:04 -0700
Subject: [PATCH 1/3] [lldb] Fix and re-enable TestUseSourceCache.py
The decorato
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/111237
>From 6756842b1c78ac6f41fa467f112aa7632f260582 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Fri, 4 Oct 2024 23:27:04 -0700
Subject: [PATCH 1/3] [lldb] Fix and re-enable TestUseSourceCache.py
The decorato
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/111237
>From 6756842b1c78ac6f41fa467f112aa7632f260582 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Fri, 4 Oct 2024 23:27:04 -0700
Subject: [PATCH 1/2] [lldb] Fix and re-enable TestUseSourceCache.py
The decorato
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/111483
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/111237
>From 6756842b1c78ac6f41fa467f112aa7632f260582 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Fri, 4 Oct 2024 23:27:04 -0700
Subject: [PATCH] [lldb] Fix and re-enable TestUseSourceCache.py
The decorators c
igorkudrin wrote:
> To make the test more representative, I suggeest replacing the `removeFile()`
> method with the following:
Thanks! I've updated the test as you suggested.
https://github.com/llvm/llvm-project/pull/111237
___
lldb-commits mailing l
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/111237
>From 6756842b1c78ac6f41fa467f112aa7632f260582 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Fri, 4 Oct 2024 23:27:04 -0700
Subject: [PATCH 1/2] [lldb] Fix and re-enable TestUseSourceCache.py
The decorato
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/111483
>From bb594335d05a4c8cb2949556f5b338242a9b5280 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Mon, 7 Oct 2024 22:07:02 -0700
Subject: [PATCH 1/2] [lldb] Fix TestGlobalModuleCache.py for remote debugging
`S
@@ -111,6 +111,8 @@ def do_test(self, one_target, one_debugger):
else:
if one_target:
new_debugger = lldb.SBDebugger().Create()
+if lldb.selected_platform is not None:
+new_debugger.SetSelectedPlatform(lldb
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/111483
>From bb594335d05a4c8cb2949556f5b338242a9b5280 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Mon, 7 Oct 2024 22:07:02 -0700
Subject: [PATCH 1/2] [lldb] Fix TestGlobalModuleCache.py for remote debugging
`S
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/111231
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/111483
`SBDebugger().Create()` returns a debugger with only the host platform in its
platform list. If the test suite is running for a remote platform, it should be
explicitly added and selected in the new debugger
igorkudrin wrote:
> I don't see any relevant changes on those files, so I don't know the where
> `openNativeFileInternal()` comes into the picture.
`getFileAux()` calls `openNativeFileForRead()` first and then passes the file
descriptor to `getOpenFileImpl()`. `openNativeFileForRead()` eventu
igorkudrin wrote:
> As I understand it, Android Studio was setting `use-source-cache:=false` so
> that users can continue to edit files on windows while lldb has them open.
>
> Judging by this patch, that may no longer be necessary. Or does that only
> apply for certain situations (certain win
igorkudrin wrote:
> Looks good, I guess. Is that constructor even necessary, given that it just
> forwards the argument to the base class, and we already have the forwarding
> `using` declaration?
The constructor looks redundant at the moment, perhaps it is just a legacy from
the early stages
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/111237
The decorators caused the main test, i.e. `test_set_use_source_cache_true()`,
to be skipped in most scenarios. It was only run on a Windows host targeting a
non-Windows remote platform, and it failed in this
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/111231
This fixes a build error with msvc for code introduced in #106442:
```
...\lldb\source\Expression\DiagnosticManager.cpp(37): error C2668:
'llvm::ErrorInfo::ErrorInfo':
ambiguous call to overloaded function
igorkudrin wrote:
Hi @JDevlieghere,
This change causes diagnostic messages to be duplicated on Windows. For example:
```
> yaml2obj.exe lldb\test\Shell\ObjectFile\ELF\minidebuginfo-no-lzma.yaml -o
> t.obj
> lldb-new.exe
(lldb) target create t.obj
(x86_64) C:\tmp\t.obj No LZMA support found for
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/106478
>From 6854730d45a2c119d2b8f71df6e22ead1c7ad5a8 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Wed, 28 Aug 2024 17:57:38 -0700
Subject: [PATCH 1/2] [lldb][AArch64] Do not crash if NT_ARM_TLS is missing
[D15
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/106478
>From 6854730d45a2c119d2b8f71df6e22ead1c7ad5a8 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Wed, 28 Aug 2024 17:57:38 -0700
Subject: [PATCH] [lldb][AArch64] Do not crash if NT_ARM_TLS is missing
[D156118
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/106478
[D156118](https://reviews.llvm.org/D156118) states that this note is always
present, but it is better to check it explicitly, as otherwise `lldb` may crash
when trying to read registers.
>From e588c3c305323
https://github.com/igorkudrin closed
https://github.com/llvm/llvm-project/pull/102263
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -1077,10 +1077,10 @@ ArchSpec ProcessElfCore::GetArchitecture() {
}
DataExtractor ProcessElfCore::GetAuxvData() {
- const uint8_t *start = m_auxv.GetDataStart();
- size_t len = m_auxv.GetByteSize();
- lldb::DataBufferSP buffer(new lldb_private::DataBufferHeap(start, len)
https://github.com/igorkudrin edited
https://github.com/llvm/llvm-project/pull/102263
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -1077,10 +1077,10 @@ ArchSpec ProcessElfCore::GetArchitecture() {
}
DataExtractor ProcessElfCore::GetAuxvData() {
- const uint8_t *start = m_auxv.GetDataStart();
- size_t len = m_auxv.GetByteSize();
- lldb::DataBufferSP buffer(new lldb_private::DataBufferHeap(start, len)
https://github.com/igorkudrin created
https://github.com/llvm/llvm-project/pull/102263
There is no need to clone the content and set extraction properties because
`m_auxv` is already in the required form.
>From d3a72694e444cf19e62bceab3234b8a338aec7b1 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/70898
>From 113c03bbf773c71d329ab2afd063753365e4ac68 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Thu, 26 Oct 2023 13:19:08 -0700
Subject: [PATCH] [YAMLParser] Unfold multi-line scalar values
Long scalar values
https://github.com/igorkudrin updated
https://github.com/llvm/llvm-project/pull/70898
>From 113c03bbf773c71d329ab2afd063753365e4ac68 Mon Sep 17 00:00:00 2001
From: Igor Kudrin
Date: Thu, 26 Oct 2023 13:19:08 -0700
Subject: [PATCH] [YAMLParser] Unfold multi-line scalar values
Long scalar values
Author: Igor Kudrin
Date: 2020-04-06T13:28:06+07:00
New Revision: a0249fe91c7ba0dabf0e8789171fb4aea5fca1cb
URL:
https://github.com/llvm/llvm-project/commit/a0249fe91c7ba0dabf0e8789171fb4aea5fca1cb
DIFF:
https://github.com/llvm/llvm-project/commit/a0249fe91c7ba0dabf0e8789171fb4aea5fca1cb.diff
L
Author: Igor Kudrin
Date: 2020-04-03T14:15:53+07:00
New Revision: f13ce15d441095493030404ab31eddb0fc08ca42
URL:
https://github.com/llvm/llvm-project/commit/f13ce15d441095493030404ab31eddb0fc08ca42
DIFF:
https://github.com/llvm/llvm-project/commit/f13ce15d441095493030404ab31eddb0fc08ca42.diff
L
Author: Igor Kudrin
Date: 2020-01-27T19:33:34+07:00
New Revision: 9a952fd462774e79d8dc514d71bf43ea0ca7f429
URL:
https://github.com/llvm/llvm-project/commit/9a952fd462774e79d8dc514d71bf43ea0ca7f429
DIFF:
https://github.com/llvm/llvm-project/commit/9a952fd462774e79d8dc514d71bf43ea0ca7f429.diff
L
Author: ikudrin
Date: Tue Aug 6 06:38:27 2019
New Revision: 368033
URL: http://llvm.org/viewvc/llvm-project?rev=368033&view=rev
Log:
Update LLDB to follow changes in llvm::DWARFDebugNames::NameIndex (4/5)
Differential Revision: https://reviews.llvm.org/D65640
Modified:
lldb/trunk/source/Plu
85 matches
Mail list logo
