https://github.com/aperez created
https://github.com/llvm/llvm-project/pull/101361
This introduces a `target.object-map` which allows us to remap module
locations, much in the same way as source mapping works today. This is useful,
for instance, when debugging coredumps, so we can replace some
https://github.com/aperez updated
https://github.com/llvm/llvm-project/pull/101361
>From 132b6fb0808385494a71c99533d7281420b743bd Mon Sep 17 00:00:00 2001
From: Alexandre Perez
Date: Wed, 31 Jul 2024 09:38:38 -0700
Subject: [PATCH] [lldb] Allow mapping object file paths
---
lldb/include/lldb/
https://github.com/aperez closed
https://github.com/llvm/llvm-project/pull/101361
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Alexandre Perez
Date: 2022-05-05T11:31:23-07:00
New Revision: eb3136f022b3e5061fe790e7886f4bb592d8a1d1
URL:
https://github.com/llvm/llvm-project/commit/eb3136f022b3e5061fe790e7886f4bb592d8a1d1
DIFF:
https://github.com/llvm/llvm-project/commit/eb3136f022b3e5061fe790e7886f4bb592d8a1d1.dif
aperez wrote:
> @aperez Thoughts on this? I think this could be useful
I think it could be useful as well.
Couple things to note though:
- If you allow for both sequences and iterators as arguments into
`lldb.Progress.track` you might not know the total number steps in advance.
- You'll need
@@ -52,6 +52,13 @@ Non-deterministic progresses behave the same, but omit the
total in the construc
# Explicitly send a progressEnd, otherwise this will be sent
# when the python runtime cleans up this object.
non_deterministic_progress.Finalize()
+
+Additionally f
