labath wrote:
> If it is, then we may just want to make this build in that configuration, but
> not actually claim to support mips debugging (in theory, you should still be
> able to debug e.g. x86 core files with a mips build of lldb)
One way to do that would be to change `#ifdef __linux__` o
DavidSpickett wrote:
I think this https://github.com/llvm/llvm-project/issues/63468 is the same sort
of issue. Not sure if it's the same though.
As you can tell from me saying "I will get back to this" 2 years ago, the
knowledge of any of that has left my head by now, but thank you for looking
oontvoo wrote:
> It might be a good idea to include something like "client_name" field so you
> can differentiate (assuming people don't lie) messages coming from lldb-dap
> from other lldb "clients".
done
https://github.com/llvm/llvm-project/pull/129728
__
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/133079
>From 2314f9e584d736ce2093cc196c7c57c2087cde42 Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 26 Mar 2025 12:54:36 +
Subject: [PATCH 1/2] [lldb][Instrumentation] Set selected frame to outside
san
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/133078
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/oontvoo updated
https://github.com/llvm/llvm-project/pull/129728
>From 21103adacdf9c08cee4065f8a6b90ff812fefbb3 Mon Sep 17 00:00:00 2001
From: Vy Nguyen
Date: Tue, 4 Mar 2025 11:01:46 -0500
Subject: [PATCH 01/16] [LLDB][Telemetry] Collect telemetry from client when
allowed.
https://github.com/DavidSpickett approved this pull request.
LGTM
Could you append to the PR description a list of known issues e.g. the redraw
on tab complete?
It's discussed here in comments already but it's good to have a record of what
state we are at and what you have promised to address
@@ -0,0 +1,171 @@
+//===-- Statusline.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: Apac
@@ -936,3 +936,7 @@ size_t StackFrameList::GetStatus(Stream &strm, uint32_t
first_frame,
strm.IndentLess();
return num_frames_displayed;
}
+
+void StackFrameList::ClearSelectedFrameIndex() {
jimingham wrote:
In StackFrameList::Clear we take the m_list_mut
https://github.com/Michael137 created
https://github.com/llvm/llvm-project/pull/133079
None
>From 2314f9e584d736ce2093cc196c7c57c2087cde42 Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 26 Mar 2025 12:54:36 +
Subject: [PATCH] [lldb][Instrumentation] Set selected frame to outside
s
labath wrote:
Sorry about the delay. I wasn't quite happy with the hedging in the
implementation, and I also wanted to write a test for it, but I figured it
would be easier if I did it myself. I now have #133093. You can rebase your
patch on top of that when it lands.
https://github.com/llvm
slydiman wrote:
> I don't see a reason for an function-local static to be a gc root.
I don't know how to check it. lld has parameters `--why-extract=` and
`--print-gc-sections`, but they are useless for this investigation.
Maybe lambdas become gc roots?
Anyway, how will this affect the accept
jimingham wrote:
Other than the question about mutexes, this looks good to me.
https://github.com/llvm/llvm-project/pull/133078
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -936,3 +936,7 @@ size_t StackFrameList::GetStatus(Stream &strm, uint32_t
first_frame,
strm.IndentLess();
return num_frames_displayed;
}
+
+void StackFrameList::ClearSelectedFrameIndex() {
Michael137 wrote:
`GetSelectedFrameIndex` modifies `m_selected_f
@@ -936,3 +936,7 @@ size_t StackFrameList::GetStatus(Stream &strm, uint32_t
first_frame,
strm.IndentLess();
return num_frames_displayed;
}
+
+void StackFrameList::ClearSelectedFrameIndex() {
Michael137 wrote:
h good question. `GetSelectedFrameIndex` i
https://github.com/labath created
https://github.com/llvm/llvm-project/pull/133072
The main change here is that we're now able to correctly look up plans for
these functions. Previously, due to caching, we could end up with one entry
covering most of the address space (because part of the func
https://github.com/JDevlieghere approved this pull request.
https://github.com/llvm/llvm-project/pull/132370
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/JDevlieghere approved this pull request.
Congrats! 🥳
https://github.com/llvm/llvm-project/pull/132923
___
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/133078
___
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/133078
The motivation for this patch is that `StopInfo::GetSuggestedStackFrameIndex`
would not take effect for `InstrumentationRuntimeStopInfo` (which we plan to
implement in TBD). This was happening because the in
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/133079
___
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: Michael Buch (Michael137)
Changes
The motivation for this patch is that `StopInfo::GetSuggestedStackFrameIndex`
would not take effect for `InstrumentationRuntimeStopInfo` (which we plan to
implement in https://github.com/llvm/llvm-project/
@@ -333,38 +333,11 @@ void Block::FinalizeRanges() {
void Block::AddRange(const Range &range) {
Block *parent_block = GetParent();
if (parent_block && !parent_block->Contains(range)) {
-Log *log = GetLog(LLDBLog::Symbols);
-if (log) {
- ModuleSP module_sp(m_par
https://github.com/labath updated
https://github.com/llvm/llvm-project/pull/117725
>From a2fe723ccfce64c3ccef67bbc75deba050d8dcc2 Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Tue, 26 Nov 2024 16:12:40 +0100
Subject: [PATCH 1/2] [lldb] Handle improperly nested blocks differently
In 6c7f561
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 976e41302411e511ab0e99922288185b5939bf54
91110b85aab9ddf41d1b52b9fc23d68883966b93 --e
slydiman wrote:
> Global variables are
> [banned](https://llvm.org/docs/CodingStandards.html#do-not-use-static-constructors)
> by the coding standards, but I wouldn't be surprised if there were still
> some around that cause this.
TypeSystemClang.cpp contains global `char TypeSystemClang::ID;
mizvekov wrote:
Thanks, this will be fixed here:
https://github.com/llvm/llvm-project/pull/133113
https://github.com/llvm/llvm-project/pull/132401
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinf
https://github.com/oontvoo updated
https://github.com/llvm/llvm-project/pull/129728
>From 21103adacdf9c08cee4065f8a6b90ff812fefbb3 Mon Sep 17 00:00:00 2001
From: Vy Nguyen
Date: Tue, 4 Mar 2025 11:01:46 -0500
Subject: [PATCH 01/17] [LLDB][Telemetry] Collect telemetry from client when
allowed.
@@ -0,0 +1,165 @@
+//===-- GoToTargetsRequestHandler.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
JDevlieghere wrote:
> Could you append to the PR description a list of known issues e.g. the redraw
> on tab complete?
>
> It's discussed here in comments already but it's good to have a record of
> what state we are at and what you have promised to address (not that I doubt
> your sincerity
@@ -94,6 +94,7 @@ struct ForkLaunchInfo {
bool debug;
bool disable_aslr;
std::string wd;
+ std::string executable;
labath wrote:
They are accessed from the forked process (line 34 in this file), so they need
to be async-signal safe (nothing really gua
@@ -94,6 +94,7 @@ struct ForkLaunchInfo {
bool debug;
bool disable_aslr;
std::string wd;
+ std::string executable;
JDevlieghere wrote:
Makes sense, thanks for explaining!
https://github.com/llvm/llvm-project/pull/133093
___
https://github.com/oontvoo updated
https://github.com/llvm/llvm-project/pull/129728
>From 21103adacdf9c08cee4065f8a6b90ff812fefbb3 Mon Sep 17 00:00:00 2001
From: Vy Nguyen
Date: Tue, 4 Mar 2025 11:01:46 -0500
Subject: [PATCH 01/18] [LLDB][Telemetry] Collect telemetry from client when
allowed.
vogelsgesang wrote:
This is probably worth mentioning in the release notes, in
`llvm/docs/ReleaseNotes.md`
https://github.com/llvm/llvm-project/pull/131820
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
ht
https://github.com/da-viper updated
https://github.com/llvm/llvm-project/pull/130503
>From 7bad765585b2ae96faf2d2558b099f4b965d2791 Mon Sep 17 00:00:00 2001
From: Ezike Ebuka
Date: Sun, 9 Mar 2025 12:46:54 +
Subject: [PATCH 01/24] [lldb-dap] implement jump to cursor.
---
lldb/cmake/module
DavidSpickett wrote:
> The tab complete issue is (should be?) fixed with the current state of this
> PR.
Cool! I did not check it again locally. If you're reasonably sure you've fixed
it then I trust you there :)
Go ahead and land this and I'll try my best to break it again at some point.
h
@@ -936,3 +936,7 @@ size_t StackFrameList::GetStatus(Stream &strm, uint32_t
first_frame,
strm.IndentLess();
return num_frames_displayed;
}
+
+void StackFrameList::ClearSelectedFrameIndex() {
jimingham wrote:
This is a shared mutex so it can't be recursive
https://github.com/da-viper updated
https://github.com/llvm/llvm-project/pull/130503
>From 7bad765585b2ae96faf2d2558b099f4b965d2791 Mon Sep 17 00:00:00 2001
From: Ezike Ebuka
Date: Sun, 9 Mar 2025 12:46:54 +
Subject: [PATCH 01/24] [lldb-dap] implement jump to cursor.
---
lldb/cmake/module
https://github.com/JDevlieghere approved this pull request.
https://github.com/llvm/llvm-project/pull/133093
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -94,6 +94,7 @@ struct ForkLaunchInfo {
bool debug;
bool disable_aslr;
std::string wd;
+ std::string executable;
JDevlieghere wrote:
This is consistent with the rest of the file, but any reason these are
`std::string`s and not `FileSpec`s?
https://g
@@ -0,0 +1,147 @@
+//===-- WriteMemoryRequestHandler.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:
JDevlieghere wrote:
I follow the argument about a custom iterator likely being more complicated,
but the callbacks aren't much better in that regard. Did you consider having
something like `GetEnabledInstances` that returns a vector with just the
enabled instances? It seems like that would be
nico wrote:
> Thanks, this will be fixed here: #133113
That also fixes an `Assertion `!isNull() && "Cannot retrieve a NULL type
pointer"' failed.` we started seeing after this here landed (repro:
https://issues.chromium.org/issues/406497227#comment3)
It'd be good if we could either land that
@@ -0,0 +1,91 @@
+//===-- GoToTargetsRequestHandler.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: Apa
@@ -0,0 +1,165 @@
+//===-- GoToTargetsRequestHandler.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/ashgti edited
https://github.com/llvm/llvm-project/pull/130503
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/JDevlieghere approved this pull request.
The comments/LLDB changes LGTM. You might want someone from OpenMP sign off on
that change as this is output someone might be relying on.
https://github.com/llvm/llvm-project/pull/133148
__
@@ -23,10 +23,240 @@
#include "llvm/Support/JSON.h"
#include
#include
+#include
#include
namespace lldb_dap::protocol {
+/// An `ExceptionBreakpointsFilter` is shown in the UI as an filter option for
+/// configuring how exceptions are dealt with.
+struct ExceptionBre
@@ -44,4 +44,223 @@ bool fromJSON(const json::Value &Params, Source &S,
json::Path P) {
O.mapOptional("sourceReference", S.sourceReference);
}
+json::Value toJSON(const ExceptionBreakpointsFilter &EBF) {
+ json::Object result{{"filter", EBF.filter}, {"label", EBF.la
@@ -54,6 +54,79 @@ bool fromJSON(const llvm::json::Value &, DisconnectArguments
&,
/// body field is required.
using DisconnectResponse = VoidResponse;
+/// Arguments for `initialize` request.
+struct InitializeRequestArguments {
+ /// The ID of the debug adapter.
+ std::st
@@ -54,6 +54,79 @@ bool fromJSON(const llvm::json::Value &, DisconnectArguments
&,
/// body field is required.
using DisconnectResponse = VoidResponse;
+/// Arguments for `initialize` request.
+struct InitializeRequestArguments {
+ /// The ID of the debug adapter.
+ std::st
@@ -23,6 +24,75 @@ bool fromJSON(const json::Value &Params, DisconnectArguments
&DA,
O.mapOptional("suspendDebuggee", DA.suspendDebuggee);
}
+bool fromJSON(const llvm::json::Value &Params,
+ InitializeRequestArguments::PathFormat &PF, llvm::json::Path P)
@@ -47,7 +48,7 @@ class BaseRequestHandler {
virtual void operator()(const protocol::Request &request) const = 0;
- virtual llvm::StringMap GetCapabilities() const { return {}; }
+ virtual std::set GetSupportedFeatures() const { return {}; }
JDevlieghere
@@ -0,0 +1,165 @@
+//===-- GoToTargetsRequestHandler.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,165 @@
+//===-- GoToTargetsRequestHandler.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
JDevlieghere wrote:
> We did consider this approach. There are some drawbacks beyond the
> performance issue, but the tradeoff may be worth it.
>
> If we define the method like: `std::vector
> GetEnabledInstances()` then we are returning copies of the PluginInstance.
> Anything that modifies
https://github.com/wizardengineer updated
https://github.com/llvm/llvm-project/pull/130516
>From 161bdb32b284d2370b138e72a8a1ad560b258ba9 Mon Sep 17 00:00:00 2001
From: medievalghoul <61852278+medievalgh...@users.noreply.github.com>
Date: Sun, 9 Mar 2025 16:20:47 -0400
Subject: [PATCH 01/15] Cha
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/132193
>From 223d85c6b2f5509f704d598bae974a98e5bf6bcb Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Thu, 20 Mar 2025 11:46:45 +
Subject: [PATCH 1/2] [lldb][debugserver][MacOSX] Work around sanitizer
misalig
ashgti wrote:
> This code seems quite repetitive. Would it be possible to have a
> `Capabilities` enum and then representing the actual values by something like
> `map` (with std::nullopt replaced by removing the
> capability from the map). Or even `map` if you don't need to
> access the capa
Author: Jonas Devlieghere
Date: 2025-03-26T14:41:05-07:00
New Revision: 9c18edc62123e778d1d713df44aa05c91e7bbbae
URL:
https://github.com/llvm/llvm-project/commit/9c18edc62123e778d1d713df44aa05c91e7bbbae
DIFF:
https://github.com/llvm/llvm-project/commit/9c18edc62123e778d1d713df44aa05c91e7bbbae.d
@@ -0,0 +1,165 @@
+//===-- GoToTargetsRequestHandler.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,118 @@
+//===-- GoToRequestHandler.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: Apache-2.
https://github.com/da-viper updated
https://github.com/llvm/llvm-project/pull/130503
>From aa8ce4da16b9cf31974eb32ecefdeab403f3a497 Mon Sep 17 00:00:00 2001
From: Ezike Ebuka
Date: Sun, 9 Mar 2025 12:46:54 +
Subject: [PATCH 01/25] [lldb-dap] implement jump to cursor.
---
lldb/cmake/module
https://github.com/da-viper updated
https://github.com/llvm/llvm-project/pull/130503
>From aa8ce4da16b9cf31974eb32ecefdeab403f3a497 Mon Sep 17 00:00:00 2001
From: Ezike Ebuka
Date: Sun, 9 Mar 2025 12:46:54 +
Subject: [PATCH 01/26] [lldb-dap] implement jump to cursor.
---
lldb/cmake/module
github-actions[bot] wrote:
Thank you for submitting a Pull Request (PR) to the LLVM Project!
This PR will be automatically labeled and the relevant teams will be notified.
If you wish to, you can add reviewers by using the "Reviewers" section on this
page.
If this is not working for you, it
llvmbot wrote:
@llvm/pr-subscribers-backend-x86
Author: Alexander Ziaee (concussious)
Changes
Increase specificity by using the correct unit sizes. KBytes is an abbreviation
for kB, 1000 bytes, and the hardware industry as well as several operating
systems have now switched to using 1000
https://github.com/wizardengineer updated
https://github.com/llvm/llvm-project/pull/130516
>From 161bdb32b284d2370b138e72a8a1ad560b258ba9 Mon Sep 17 00:00:00 2001
From: medievalghoul <61852278+medievalgh...@users.noreply.github.com>
Date: Sun, 9 Mar 2025 16:20:47 -0400
Subject: [PATCH 01/13] Cha
https://github.com/wizardengineer updated
https://github.com/llvm/llvm-project/pull/130516
>From 161bdb32b284d2370b138e72a8a1ad560b258ba9 Mon Sep 17 00:00:00 2001
From: medievalghoul <61852278+medievalgh...@users.noreply.github.com>
Date: Sun, 9 Mar 2025 16:20:47 -0400
Subject: [PATCH 01/14] Cha
wizardengineer wrote:
> You could even write a wrapper for that test that creates a Status from the
> error and imitates the old API, just inside the unit tests.
how would i go about doing that?
https://github.com/llvm/llvm-project/pull/130516
___
l
https://github.com/jasonmolenda approved this pull request.
LGTM.
https://github.com/llvm/llvm-project/pull/133072
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/wizardengineer updated
https://github.com/llvm/llvm-project/pull/130516
>From 161bdb32b284d2370b138e72a8a1ad560b258ba9 Mon Sep 17 00:00:00 2001
From: medievalghoul <61852278+medievalgh...@users.noreply.github.com>
Date: Sun, 9 Mar 2025 16:20:47 -0400
Subject: [PATCH 1/9] Chang
jasonmolenda wrote:
Sorry for not commenting last week when this issue was live, but with regards
to Apple silicon macs, there was a kernel behavior where watchpoints and
hardware breakpoints were disabled by the kernel when it was single instruction
stepping. I believe this was fixed in macO
https://github.com/satyajanga updated
https://github.com/llvm/llvm-project/pull/130841
>From e949d2ee19408c43d9067075d2436f8549132830 Mon Sep 17 00:00:00 2001
From: satya janga
Date: Tue, 11 Mar 2025 13:39:08 -0700
Subject: [PATCH 1/4] Make breakpoint stop reason more accurate
---
.../test/to
llvmbot wrote:
@llvm/pr-subscribers-lld-elf
Author: Alexander Ziaee (concussious)
Changes
Increase specificity by using the correct unit sizes. KBytes is an abbreviation
for kB, 1000 bytes, and the hardware industry as well as several operating
systems have now switched to using 1000 byt
llvmbot wrote:
@llvm/pr-subscribers-lld
Author: Alexander Ziaee (concussious)
Changes
Increase specificity by using the correct unit sizes. KBytes is an abbreviation
for kB, 1000 bytes, and the hardware industry as well as several operating
systems have now switched to using 1000 byte kB
https://github.com/concussious created
https://github.com/llvm/llvm-project/pull/133148
Increase specificity by using the correct unit sizes. KBytes is an abbreviation
for kB, 1000 bytes, and the hardware industry as well as several operating
systems have now switched to using 1000 byte kBs.
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 8f863fcd77e15caf3b7fde089adc223b0c4fb103
7ebfa965e0210a95f3fa65e1fc373a98d350a8a8 --e
https://github.com/da-viper edited
https://github.com/llvm/llvm-project/pull/130503
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/121860
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
labath wrote:
@yuvald-sweet-security
https://github.com/llvm/llvm-project/pull/133093
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dmpots wrote:
> Did you consider having something like `GetEnabledInstances` that returns a
> vector with just the enabled instances? It seems like that would be a lot
> less intrusive and I'd be surprised if this code is hot enough that the
> overhead of creating a new vector instead of retur
@@ -0,0 +1,165 @@
+//===-- GoToTargetsRequestHandler.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,165 @@
+//===-- GoToTargetsRequestHandler.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,165 @@
+//===-- GoToTargetsRequestHandler.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/wizardengineer updated
https://github.com/llvm/llvm-project/pull/130516
>From 161bdb32b284d2370b138e72a8a1ad560b258ba9 Mon Sep 17 00:00:00 2001
From: medievalghoul <61852278+medievalgh...@users.noreply.github.com>
Date: Sun, 9 Mar 2025 16:20:47 -0400
Subject: [PATCH 01/18] Cha
https://github.com/wizardengineer updated
https://github.com/llvm/llvm-project/pull/130516
>From 161bdb32b284d2370b138e72a8a1ad560b258ba9 Mon Sep 17 00:00:00 2001
From: medievalghoul <61852278+medievalgh...@users.noreply.github.com>
Date: Sun, 9 Mar 2025 16:20:47 -0400
Subject: [PATCH 01/19] Cha
@@ -0,0 +1,104 @@
+//===-- DILParser.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,238 @@
+//===-- DILEval.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
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Pavel Labath (labath)
Changes
The main change here is that we're now able to correctly look up plans for
these functions. Previously, due to caching, we could end up with one entry
covering most of the address space (because part of the fu
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 1a7402d3d831940fc04cc0fb5731239744ce5435
b68ee05934778f77bf27f8b6716e1db564bd4f98 --e
https://github.com/labath updated
https://github.com/llvm/llvm-project/pull/133072
>From 3bc6ae141f31a1e09e45c648464e3804a7734a2c Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Wed, 26 Mar 2025 12:46:28 +0100
Subject: [PATCH] [lldb] Teach FuncUnwinders about discontinuous functions
The main
labath wrote:
> This type of patch also slightly worries me in that it could make it harder
> to unify the LLDB dwarf data structures with the LLVM ones
That is something I considered, but I think this might actually help with that.
At this point the LLDB and llvm dwarf classes are so differen
@@ -0,0 +1,273 @@
+//===-- DILParser.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,276 @@
+//===-- DILParser.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 edited
https://github.com/llvm/llvm-project/pull/120971
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,131 @@
+//===-- DILParser.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
https://github.com/labath commented:
> * Based on the way DiagnosticError is use, I've created a new error
> class, DILDiagnosticError, patterned after the OptionParserError clas, which
> DOES make use of DiagnosticError.
The class implementation looks okay for the most part.
> * I ha
https://github.com/DavidSpickett edited
https://github.com/llvm/llvm-project/pull/117725
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,100 @@
+## This test checks that lldb handles (corrupt?) debug info which has
improperly
+## nested blocks. The behavior here is not prescriptive. We only want to check
+## that we do something "reasonable".
+
+
+# RUN: llvm-mc -triple=x86_64-pc-linux -filetype=obj %s
@@ -0,0 +1,100 @@
+## This test checks that lldb handles (corrupt?) debug info which has
improperly
+## nested blocks. The behavior here is not prescriptive. We only want to check
DavidSpickett wrote:
Could you add comments somewhere in this file that note where
1 - 100 of 121 matches
Mail list logo
