https://github.com/labath approved this pull request.
I believe these weren't functional for a very long time now.
https://github.com/llvm/llvm-project/pull/108629
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin
https://github.com/labath approved this pull request.
https://github.com/llvm/llvm-project/pull/106774
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/labath commented:
Actually, the CI failure appears to be relevant. The error path in the test is
`errno->std::error_code->Status->Expected` and the code in `CheckIPSupport`
expects to get a `llvm::ECError`.
It looks like it gets a different type now, and I think that's probab
labath wrote:
> * Everyone (else) I talked to liked the idea of reusing the logging system
> because that's what we already use and are familiar with. Promoting a log
> message to be part of this log becomes as easy as adding a `GetLog` and using
> the same macro.
I'm all for code reuse, and
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/96538
>From 16ae2c3c04d908807d78224a8fee34f772a337fa Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Mon, 29 Jan 2024 16:23:16 +
Subject: [PATCH 1/4] [lldb] Support new libc++ __compressed_pair layout
---
ll
Author: Michael Buch
Date: 2024-09-16T10:11:49+01:00
New Revision: 9e9b1178ca435f690381ffe8241e4bf1bb7e60fb
URL:
https://github.com/llvm/llvm-project/commit/9e9b1178ca435f690381ffe8241e4bf1bb7e60fb
DIFF:
https://github.com/llvm/llvm-project/commit/9e9b1178ca435f690381ffe8241e4bf1bb7e60fb.diff
https://github.com/Michael137 closed
https://github.com/llvm/llvm-project/pull/96538
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Michael Buch
Date: 2024-09-16T10:15:52+01:00
New Revision: 7e5fe3ec5aed001c3b8f0bf59167b6472b91b9cc
URL:
https://github.com/llvm/llvm-project/commit/7e5fe3ec5aed001c3b8f0bf59167b6472b91b9cc
DIFF:
https://github.com/llvm/llvm-project/commit/7e5fe3ec5aed001c3b8f0bf59167b6472b91b9cc.diff
https://github.com/Michael137 closed
https://github.com/llvm/llvm-project/pull/108629
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/labath created
https://github.com/llvm/llvm-project/pull/108806
This can legitimately happen for static function-local variables with a
non-manual dwarf index. According to the DWARF spec, these variables should be
(and are) included in the compiler generated indexes, but th
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Pavel Labath (labath)
Changes
This can legitimately happen for static function-local variables with a
non-manual dwarf index. According to the DWARF spec, these variables should be
(and are) included in the compiler generated indexes, but
https://github.com/labath created
https://github.com/llvm/llvm-project/pull/108810
Use a `nullptr` map entry to mean "variable parse was attempted and it failed"
an the absence of an entry to mean "parsing hasn't been attempted yet".
I ran into this because parsing of function-static variables
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Pavel Labath (labath)
Changes
Use a `nullptr` map entry to mean "variable parse was attempted and it failed"
an the absence of an entry to mean "parsing hasn't been attempted yet".
I ran into this because parsing of function-static variabl
@@ -124,6 +124,9 @@ class ABISysV_riscv : public lldb_private::RegInfoBasedABI {
using lldb_private::RegInfoBasedABI::RegInfoBasedABI; // Call CreateInstance
// instead.
bool m_is_rv64; // true if target is riscv64; fa
https://github.com/dlav-sc updated
https://github.com/llvm/llvm-project/pull/99336
>From 10d7addd0a86789e268189e00a825af27516323e Mon Sep 17 00:00:00 2001
From: Daniil Avdeev
Date: Thu, 11 Jul 2024 11:21:36 +
Subject: [PATCH 1/5] [lldb][RISCV] add jitted function calls to ABI
Function call
@@ -164,11 +167,82 @@ TotalArgsSizeInWords(bool is_rv64,
return total_size;
}
+static bool UpdateRegister(RegisterContext *reg_ctx,
+ const lldb::RegisterKind reg_kind,
+ const uint32_t reg_num, const addr_t value) {
+ Log
@@ -164,11 +167,82 @@ TotalArgsSizeInWords(bool is_rv64,
return total_size;
}
+static bool UpdateRegister(RegisterContext *reg_ctx,
+ const lldb::RegisterKind reg_kind,
+ const uint32_t reg_num, const addr_t value) {
+ Log
https://github.com/sylvestre edited
https://github.com/llvm/llvm-project/pull/108719
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -124,6 +124,9 @@ class ABISysV_riscv : public lldb_private::RegInfoBasedABI {
using lldb_private::RegInfoBasedABI::RegInfoBasedABI; // Call CreateInstance
// instead.
bool m_is_rv64; // true if target is riscv64; fa
https://github.com/Michael137 commented:
Seems reasonable to make this less spammy. Though is there a reason why we're
not adding them to the manual index? Is this just something we didn't implement
(yet)?
https://github.com/llvm/llvm-project/pull/108806
___
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/99012
>From 8d0245dfccc607a4237fc94bbbfea646fa1a6887 Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 10 Jul 2024 15:37:45 +0100
Subject: [PATCH 1/4] [WIP][lldb][test] Add a new __compressed_pair layout to
li
Author: Michael Buch
Date: 2024-09-16T12:05:00+01:00
New Revision: 9548dbedbc1b2bfb130c91df54e8007acb81e1b0
URL:
https://github.com/llvm/llvm-project/commit/9548dbedbc1b2bfb130c91df54e8007acb81e1b0
DIFF:
https://github.com/llvm/llvm-project/commit/9548dbedbc1b2bfb130c91df54e8007acb81e1b0.diff
labath wrote:
Adding these to the manual index is very easy -- there just isn't a point in
doing it (except maybe for consistency).
In case I wasn't clear: this warning/error appears in the compiler-generated
indexes, because we find the variable in the name lookup -- and then ignore it.
For t
labath wrote:
One more clarification :P
I think it would be reasonable for something like `target variable foo()::v` to
return the static variable `v` in function `foo()`, and to make that work we
might (depending on how exactly this is implemented) need to insert the
variable into the manual
@@ -1364,8 +1364,14 @@ void request_evaluate(const llvm::json::Object &request)
{
std::string expression = GetString(arguments, "expression").str();
llvm::StringRef context = GetString(arguments, "context");
- if (context == "repl" && g_dap.DetectExpressionContext(frame,
Michael137 wrote:
Ahh thanks for the clarification. Makes sense.
Sounds like a situation where this would arise is:
```
struct Foo {
static int bar;
};
int Foo::bar = 5;
int main() {
static bool bar = false
__builtin_debugtrap();
}
```
Doing `(lldb) target var bar` would produce this er
https://github.com/Michael137 approved this pull request.
https://github.com/llvm/llvm-project/pull/108806
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -3828,10 +3828,8 @@ void SymbolFileDWARF::ParseAndAppendGlobalVariable(
break;
default:
-GetObjectFile()->GetModule()->ReportError(
-"didn't find appropriate parent DIE for variable list for {0:x8} "
-"{1} ({2}).\n",
-die.GetID(), DW_TAG_va
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/99012
>From 8d0245dfccc607a4237fc94bbbfea646fa1a6887 Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 10 Jul 2024 15:37:45 +0100
Subject: [PATCH 1/5] [WIP][lldb][test] Add a new __compressed_pair layout to
li
dlav-sc wrote:
@JDevlieghere @jasonmolenda @labath @tedwoodward could you take another look,
please.
https://github.com/llvm/llvm-project/pull/99336
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listi
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/104317
>From 88b48a5df0153a44276f14872c48e10639dcb673 Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Wed, 14 Aug 2024 11:52:40 +
Subject: [PATCH 1/9] [lldb-dap] Support inspecting memory
Adds suppor
Author: Michael Buch
Date: 2024-09-16T13:46:19+01:00
New Revision: 765e106fb1b0e0aeb1bba18dfd93bd28233bba2f
URL:
https://github.com/llvm/llvm-project/commit/765e106fb1b0e0aeb1bba18dfd93bd28233bba2f
DIFF:
https://github.com/llvm/llvm-project/commit/765e106fb1b0e0aeb1bba18dfd93bd28233bba2f.diff
https://github.com/Michael137 closed
https://github.com/llvm/llvm-project/pull/99012
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/104317
>From 88b48a5df0153a44276f14872c48e10639dcb673 Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Wed, 14 Aug 2024 11:52:40 +
Subject: [PATCH 01/10] [lldb-dap] Support inspecting memory
Adds supp
vogelsgesang wrote:
@clayborg the code is now up-to-date and ready for another review 🙂
https://github.com/llvm/llvm-project/pull/104317
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-com
dfukalov wrote:
Gentle ping...
https://github.com/llvm/llvm-project/pull/106810
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Michael137 created
https://github.com/llvm/llvm-project/pull/108825
This attempts to improve user-experience when LLDB stops on a verbose_trap.
Currently if a `__builtin_verbose_trap` triggers, we display the first frame
above the call to the verbose_trap. So in the newly ad
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Michael Buch (Michael137)
Changes
This attempts to improve user-experience when LLDB stops on a verbose_trap.
Currently if a `__builtin_verbose_trap` triggers, we display the first frame
above the call to the verbose_trap. So in the newly
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/108825
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -1376,6 +1382,16 @@ void request_evaluate(const llvm::json::Object &request)
{
EmplaceSafeString(body, "result", result);
body.try_emplace("variablesReference", (int64_t)0);
} else {
+if (context == "repl") {
+ // If the expression is empty and the last e
https://github.com/walter-erquinigo approved this pull request.
https://github.com/llvm/llvm-project/pull/108719
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -78,7 +78,7 @@ bool CommandObjectThreadTraceStartIntelPT::DoExecuteOnThreads(
llvm::ArrayRef tids) {
if (Error err = m_trace.Start(tids, m_options.m_ipt_trace_size,
m_options.m_enable_tsc,
m_options.m_psb_period))
-result.SetError(S
https://github.com/cmtice updated
https://github.com/llvm/llvm-project/pull/107485
>From 15541f354decf80586d590db9f9cb353be04b122 Mon Sep 17 00:00:00 2001
From: Caroline Tice
Date: Thu, 5 Sep 2024 15:51:35 -0700
Subject: [PATCH 1/7] [lldb-dap] Add feature to remember last non-empty
expression.
https://github.com/ldionne commented:
I'm not qualified to review the implementation, but I like the result!
https://github.com/llvm/llvm-project/pull/108825
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailm
@@ -1364,8 +1364,14 @@ void request_evaluate(const llvm::json::Object &request)
{
std::string expression = GetString(arguments, "expression").str();
llvm::StringRef context = GetString(arguments, "context");
- if (context == "repl" && g_dap.DetectExpressionContext(frame,
@@ -3064,22 +3064,41 @@ static int gdb_errno_to_system(int err) {
static uint64_t ParseHostIOPacketResponse(StringExtractorGDBRemote &response,
uint64_t fail_result, Status &error)
{
+ // The packet is expected to have the following
https://github.com/kusmour updated
https://github.com/llvm/llvm-project/pull/108719
>From 9f41e2a32f1800a9d98a749cf109d9a3072e2210 Mon Sep 17 00:00:00 2001
From: Wanyi Ye
Date: Sat, 14 Sep 2024 14:23:01 -0700
Subject: [PATCH] [lldb][intel-pt] Fix build error on conversion from
llvm::Error to S
https://github.com/Jlalond approved this pull request.
https://github.com/llvm/llvm-project/pull/108719
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
cmtice wrote:
Ping? Anybody?
https://github.com/llvm/llvm-project/pull/95738
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Michael137 wrote:
Is the plan to get the DIL data structures merged before the rest of the patch
series is up for review? I think it'd be great to see how the infrastructure
introduced here will be used
https://github.com/llvm/llvm-project/pull/95738
___
https://github.com/vogelsgesang created
https://github.com/llvm/llvm-project/pull/108870
This commit changes the libc++ frame recognizer to hide implementation details
of libc++ more aggressively. The applied heuristic is rather straightforward:
We consider every function name starting with `_
llvmbot wrote:
@llvm/pr-subscribers-lldb
@llvm/pr-subscribers-libcxx
Author: Adrian Vogelsgesang (vogelsgesang)
Changes
This commit changes the libc++ frame recognizer to hide implementation details
of libc++ more aggressively. The applied heuristic is rather straightforward:
We consider
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
6d3f6c2170dd60e86743c205e33ead2f455656b4...f0ffdc6f1d999dc3c774f1d42d03db286705c1b5
lldb
tru wrote:
/cherry-pick adf44d5c3ea03569f019740e1140c3205810b3fa
2bcab9ba7139cfa96c85433fa85b29c8a6d7008b
https://github.com/llvm/llvm-project/pull/106885
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman
andrurogerz wrote:
@labath there have been no additional comments; is there anyone specifically
you'd like me to seek feedback from?
@JDevlieghere would you have a moment to take a look at this PR soon? I really
appreciate it.
@compnerd FYI
https://github.com/llvm/llvm-project/pull/106443
__
https://github.com/clayborg approved this pull request.
Thanks for doing the modification. LGTM
https://github.com/llvm/llvm-project/pull/104317
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/l
@@ -1,81 +1,59 @@
NDK_ROOT := $(shell dirname $(CC))/../../../../..
-ifeq "$(findstring 64, $(ARCH))" "64"
- # lowest 64-bit API level
- API_LEVEL := 21
-else ifeq "$(ARCH)" "i386"
- # clone(2) declaration is present only since this api level
- API_LEVEL
https://github.com/ldionne commented:
This feels like a good idea, but I am also a bit scared of hiding too much
stuff and making it difficult to figure out what's going wrong from a stack
trace. It's not rational, I have no evidence to back this up and perhaps this
is only fear of unknown.
F
Author: Adrian Vogelsgesang
Date: 2024-09-16T22:56:20+02:00
New Revision: 3acb1eac5eb6ef4e60dd64b7845615e076cc6a3e
URL:
https://github.com/llvm/llvm-project/commit/3acb1eac5eb6ef4e60dd64b7845615e076cc6a3e
DIFF:
https://github.com/llvm/llvm-project/commit/3acb1eac5eb6ef4e60dd64b7845615e076cc6a3e
https://github.com/vogelsgesang closed
https://github.com/llvm/llvm-project/pull/104317
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/adrian-prantl updated
https://github.com/llvm/llvm-project/pull/106774
>From 141b8cec8c266c7857c38e5da76ab538ac35c706 Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Wed, 11 Sep 2024 10:35:37 +0200
Subject: [PATCH 1/2] [lldb] Only send "posix" error codes through the
gdb-r
cmtice wrote:
> Is the plan to get the DIL data structures merged before the rest of the
> patch series is up for review? I think it'd be great to see how the
> infrastructure introduced here will be used
There are 3 major pieces to the DIL implementation (soon to be 4, once I've got
the lexe
https://github.com/clayborg approved this pull request.
https://github.com/llvm/llvm-project/pull/108309
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Jacob Lalonde
Date: 2024-09-16T15:13:35-07:00
New Revision: 0975e2ac58b6d62429d51df54911fb4d03dcda05
URL:
https://github.com/llvm/llvm-project/commit/0975e2ac58b6d62429d51df54911fb4d03dcda05
DIFF:
https://github.com/llvm/llvm-project/commit/0975e2ac58b6d62429d51df54911fb4d03dcda05.diff
https://github.com/Jlalond closed
https://github.com/llvm/llvm-project/pull/108309
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
vogelsgesang wrote:
@adrian-prantl Now that https://github.com/llvm/llvm-project/pull/105695 is
merged, do you still want to open a follow-up pull request to change the
assert-recognizer and the verbose-trap-recognizer to use `ePreferMangled`?
https://github.com/llvm/llvm-project/pull/105756
_
https://github.com/clayborg approved this pull request.
https://github.com/llvm/llvm-project/pull/102928
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/adrian-prantl updated
https://github.com/llvm/llvm-project/pull/106774
>From 34a856d47322cd35a7b568a335adbcd804f2302d Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Wed, 11 Sep 2024 10:35:37 +0200
Subject: [PATCH 1/3] [lldb] Only send "posix" error codes through the
gdb-r
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/102928
>From 7dfcc909b97efe61e3af8bb9468ddc973f19b52d Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Sat, 10 Aug 2024 23:59:55 +
Subject: [PATCH] [lldb-dap] Implement declaration locations
This comm
https://github.com/adrian-prantl updated
https://github.com/llvm/llvm-project/pull/106470
>From 34a856d47322cd35a7b568a335adbcd804f2302d Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Wed, 11 Sep 2024 10:35:37 +0200
Subject: [PATCH 1/4] [lldb] Only send "posix" error codes through the
gdb-r
https://github.com/vogelsgesang closed
https://github.com/llvm/llvm-project/pull/102928
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Adrian Vogelsgesang
Date: 2024-09-17T02:18:52+02:00
New Revision: 0cc2cd781594aec741f7262df7a48d73a7d09a18
URL:
https://github.com/llvm/llvm-project/commit/0cc2cd781594aec741f7262df7a48d73a7d09a18
DIFF:
https://github.com/llvm/llvm-project/commit/0cc2cd781594aec741f7262df7a48d73a7d09a18
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/5111
Here is the relevant pi
https://github.com/jeffreytan81 created
https://github.com/llvm/llvm-project/pull/108907
## Context
We have a customer reporting scenario that expanding "this" pointer for a
non-trivial class method context takes more than **70~90 seconds**. This is a
linux target with .debug_names index table
jasonmolenda wrote:
Thanks so much for putting together the patch for this. Yeah enabling these
registers only when the thread flavor is available is not that simple, and I
don't think the consequence of including them with zero values in all cases is
bad one. Most general users will not be
https://github.com/jasonmolenda approved this pull request.
https://github.com/llvm/llvm-project/pull/108663
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/jeffreytan81 edited
https://github.com/llvm/llvm-project/pull/108907
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/jeffreytan81 updated
https://github.com/llvm/llvm-project/pull/108907
>From 6e84ab9a14e63c58e1facdbf9a695c093882b37b Mon Sep 17 00:00:00 2001
From: jeffreytan81
Date: Mon, 19 Aug 2024 10:57:35 -0700
Subject: [PATCH 1/5] Fix StartDebuggingRequestHandler/ReplModeRequestHandler
https://github.com/jeffreytan81 ready_for_review
https://github.com/llvm/llvm-project/pull/108907
___
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 (jeffreytan81)
Changes
## Context
We have a customer reporting scenario that expanding "this" pointer for a
non-trivial class method context takes more than **70~90 seconds**. This is a
linux target with .debug_names index table enabl
https://github.com/jeffreytan81 edited
https://github.com/llvm/llvm-project/pull/108907
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/compnerd approved this pull request.
https://github.com/llvm/llvm-project/pull/106443
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
vogelsgesang wrote:
The above test failure above is in `lld`, not `lldb`. I don't see how this
could have been caused by my change to `lldb-dap`
https://github.com/llvm/llvm-project/pull/102928
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/104589
>From 72c725469268d0bd39666d20f94404f81a0cb7ad Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Mon, 12 Aug 2024 14:53:31 +
Subject: [PATCH] [lldb-dap] Implement value locations for function poi
https://github.com/vogelsgesang edited
https://github.com/llvm/llvm-project/pull/104589
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/104589
>From 79684ccb2b6312b0938de73641e89d7cd29ce1a8 Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Mon, 12 Aug 2024 14:53:31 +
Subject: [PATCH] [lldb-dap] Implement value locations for function poi
https://github.com/vogelsgesang ready_for_review
https://github.com/llvm/llvm-project/pull/104589
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
vogelsgesang wrote:
Now that #102928 landed, this commit is also ready for review
https://github.com/llvm/llvm-project/pull/104589
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
88 matches
Mail list logo
