https://github.com/clayborg edited
https://github.com/llvm/llvm-project/pull/104532
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/clayborg commented:
Seems pretty clean, but we need to get Jim's opinion in case there is a better
way to do this that he would prefer.
https://github.com/llvm/llvm-project/pull/104532
___
lldb-commits mailing list
lldb-commits@list
@@ -103,6 +103,12 @@ bool ThreadPlanStepOverBreakpoint::ShouldStop(Event
*event_ptr) {
bool ThreadPlanStepOverBreakpoint::StopOthers() { return true; }
+// The ThreadPlanSingleThreadTimeout can interrupt and resume all threads
during
+// stepping, which may cause them to mi
labath wrote:
Okay, that sort of makes sense. However, unless you actually want to be able to
disable each of these plugins independently (which it sounds like you don't),
then this is a very.. baroque way to achieve the desired effect (to have
multiple (plugin) classes registered with the plu
labath wrote:
Thanks for looking into this. I'll also defer to Jim, but I'll note two things:
- stepping over a breakpoint can still block -- if the breakpoint is on a
syscall instruction, and the syscall blocks. However, problem with missed
breakpoints is also real, and probably more important
https://github.com/labath edited
https://github.com/llvm/llvm-project/pull/101086
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/labath commented:
A couple of small things, but I think it's fine overall. I'm going to be OOO
next week, no need to wait for me.
https://github.com/llvm/llvm-project/pull/101086
___
lldb-commits mailing list
lldb-commits@lists.llvm
@@ -457,34 +456,24 @@ MinidumpParser::FindMemoryRange(lldb::addr_t addr) {
}
}
- // Some Minidumps have a Memory64ListStream that captures all the heap memory
- // (full-memory Minidumps). We can't exactly use the same loop as above,
- // because the Minidump uses sl
@@ -553,53 +547,49 @@ static bool
CreateRegionsCacheFromMemoryList(MinidumpParser &parser,
std::vector ®ions) {
Log *log = GetLog(LLDBLog::Modules);
+ // Cache the expected memory32 into an optional
+ // because double checking the expected
@@ -457,34 +456,24 @@ MinidumpParser::FindMemoryRange(lldb::addr_t addr) {
}
}
- // Some Minidumps have a Memory64ListStream that captures all the heap memory
- // (full-memory Minidumps). We can't exactly use the same loop as above,
- // because the Minidump uses sl
labath wrote:
Can those swift libraries be found automatically? For example if they're at
some known path relative to lldb or the swift compiler?
https://github.com/llvm/llvm-project/pull/104514
___
lldb-commits mailing list
lldb-commits@lists.llvm.or
https://github.com/labath approved this pull request.
https://github.com/llvm/llvm-project/pull/104109
___
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/104439
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -47,111 +48,10 @@ using namespace llvm;
// option descriptors for getopt_long_only()
-#ifdef _WIN32
-typedef pipe_t shared_fd_t;
-const shared_fd_t kInvalidSharedFD = LLDB_INVALID_PIPE;
-#else
-typedef NativeSocket shared_fd_t;
-const shared_fd_t kInvalidSharedFD = Socket:
@@ -601,15 +570,24 @@ int main_platform(int argc, char *argv[]) {
// If not running as a server, this process will not accept
// connections while a connection is active.
acceptor_up.reset();
-
- // When not running in server mode, use all available ports
https://github.com/labath edited
https://github.com/llvm/llvm-project/pull/104238
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
DavidSpickett wrote:
Only had time to build so far but:
```
/home/davspi01/work/open_source/llvm-project/lldb/tools/lldb-server/lldb-platform.cpp:
In function ‘int main_platform(int, char**)’:
/home/davspi01/work/open_source/llvm-project/lldb/tools/lldb-server/lldb-platform.cpp:354:49:
warning:
@@ -20,6 +20,10 @@
#include
#include
+#ifdef SendMessage
+#undef SendMessage
+#endif
+
labath wrote:
If it's just due to header moves that's fine.
It's definitely possible to isolate the windows headers. Lllvm does that by
making sure it only includes the
@@ -666,7 +756,23 @@ ConnectionStatus
ConnectionFileDescriptor::ConnectFD(llvm::StringRef s,
socket_id_callback_type socket_id_callback,
Status *error_ptr) {
-#if LLDB_ENABLE_POSIX
+#ifdef _WIN32
+ int64_t
DavidSpickett wrote:
> with this log
If there are a few (< 10 maybe) specific lines from the log that are the key
ones, please include those in the PR description. Just because there's a slim
chance someone in the future might have their own strange timeouts and it would
be a useful clue.
If
Author: Dmitry Vasilyev
Date: 2024-08-16T13:46:45+04:00
New Revision: 899a3df02427086f365e1308fd11ca8ab981e9df
URL:
https://github.com/llvm/llvm-project/commit/899a3df02427086f365e1308fd11ca8ab981e9df
DIFF:
https://github.com/llvm/llvm-project/commit/899a3df02427086f365e1308fd11ca8ab981e9df.dif
https://github.com/slydiman closed
https://github.com/llvm/llvm-project/pull/104439
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
slydiman wrote:
> I think this warning was already there, I'm just seeing it now in a clean
> build. `u` means `unsigned` and `portnum` is `uint16_t`.
I will revert the original definition `#define HIGH_PORT (49151u)`. Thanks.
https://github.com/llvm/llvm-project/pull/104238
_
https://github.com/vogelsgesang edited
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/vogelsgesang edited
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/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/102928
>From a740c6918fd4c0e47b6d266fbb2b217112405a4f 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/vogelsgesang ready_for_review
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
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Adrian Vogelsgesang (vogelsgesang)
Changes
This commit implements support for the "declaration location" recently added by
microsoft/debug-adapter-protocol#494 to the debug adapter protocol.
For the `declarationLocationReference` we need a
vogelsgesang wrote:
Ok, this is ready for review now. The upstream protocol changes were merged in
the meantime.
I did leave in the `$__lldb_extensions.declaration` although it is superseded
by the `declarationLocationReference`. Let me know in case you prefer me to
remove it
https://github.
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
82ee31f75ac1316006fa9e21dddfddec37cf7072...a740c6918fd4c0e47b6d266fbb2b217112405a4f
lldb/
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 82ee31f75ac1316006fa9e21dddfddec37cf7072
a740c6918fd4c0e47b6d266fbb2b217112405a4f --e
@@ -147,15 +147,8 @@ GDB-SERVER CONNECTIONS
.. option:: --gdbserver-port
- Define a port to be used for gdb-server connections. Can be specified multiple
- times to allow multiple ports. Has no effect if --min-gdbserver-port
- and --max-gdbserver-port are specified.
-
-.. op
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/102928
>From a740c6918fd4c0e47b6d266fbb2b217112405a4f Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Sat, 10 Aug 2024 23:59:55 +
Subject: [PATCH 1/2] [lldb-dap] Implement declaration locations
This
@@ -666,7 +756,23 @@ ConnectionStatus
ConnectionFileDescriptor::ConnectFD(llvm::StringRef s,
socket_id_callback_type socket_id_callback,
Status *error_ptr) {
-#if LLDB_ENABLE_POSIX
+#ifdef _WIN32
+ int64_t
DavidSpickett wrote:
I did some testing with my usual setup which is x86 Linux to AArch64 Linux
running in a simulator.
```
$ ./lldb-server platform --server --listen 0.0.0.0:1234 --gdbserver-port 49140
$ ./bin/lldb-dotest --platform-name remote-linux --platform-url
connect://172.17.0.2:1234
vogelsgesang wrote:
@JDevlieghere it seems that the automation for publishing a new VS-Code
extension to the MarketPlace did not kick off automatically. Could you dispatch
the "Publish to VSCode Marketplace" flow manually?
https://github.com/llvm/llvm-project/pull/103482
__
@@ -147,15 +147,8 @@ GDB-SERVER CONNECTIONS
.. option:: --gdbserver-port
- Define a port to be used for gdb-server connections. Can be specified multiple
- times to allow multiple ports. Has no effect if --min-gdbserver-port
- and --max-gdbserver-port are specified.
-
-.. op
slydiman wrote:
> And everything works as expected. I don't normally run remote tests with
> `ninja check-lldb`, so I just ran the above command in a couple of terminals
> at the same time and there weren't any problems.
Note we are testing
- API, Shell, unittests locally on Windows x86_64
-
@@ -4028,6 +4049,154 @@ void request_disassemble(const llvm::json::Object
&request) {
response.try_emplace("body", std::move(body));
g_dap.SendJSON(llvm::json::Value(std::move(response)));
}
+
+// "ReadMemoryRequest": {
+// "allOf": [ { "$ref": "#/definitions/Request" },
https://github.com/vogelsgesang edited
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/slydiman edited
https://github.com/llvm/llvm-project/pull/104238
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
DavidSpickett wrote:
Can you remind me what vpr is as opposed to fpr, is that V as in Vector?
https://github.com/llvm/llvm-project/pull/104547
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lld
https://github.com/DavidSpickett edited
https://github.com/llvm/llvm-project/pull/104547
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/DavidSpickett commented:
Using the "dynamic" (as aarch64 calls it) regset idea is certainly the way to
go. AArch64 has a bit of a strange setup where we have 2 fixed layouts, then
everything else is optional. Possibly it needs to be this way because of SVE
changing length, I
@@ -760,6 +772,61 @@ def test_riscv64_regs(self):
self.expect("register read --all")
+@skipIfLLVMTargetMissing("RISCV")
DavidSpickett wrote:
If everything is optional in risc-v, it may be better to label these tests by
what they contain not what
@@ -760,6 +772,61 @@ def test_riscv64_regs(self):
self.expect("register read --all")
DavidSpickett wrote:
(I can't comment on lines that aren't in the diff, booo)
Should the existing test have some new values added to the fp regs? I see that
you didn
DavidSpickett wrote:
Also consider adding "for riscv64" to the PR title, so it is clear to readers
that 32 bit is not included.
https://github.com/llvm/llvm-project/pull/104547
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.ll
https://github.com/DavidSpickett edited
https://github.com/llvm/llvm-project/pull/104547
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -760,6 +772,61 @@ def test_riscv64_regs(self):
self.expect("register read --all")
+@skipIfLLVMTargetMissing("RISCV")
DavidSpickett wrote:
AArch64 has been saved from this problem by a lot of the new register state
being weird enough it doesn'
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/104317
>From a5b4f6e7e105d36b82f9de588d2705ad3d622953 Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Wed, 14 Aug 2024 11:52:40 +
Subject: [PATCH 1/6] [lldb-dap] Support inspecting memory
Adds suppor
@@ -4028,6 +4049,154 @@ void request_disassemble(const llvm::json::Object
&request) {
response.try_emplace("body", std::move(body));
g_dap.SendJSON(llvm::json::Value(std::move(response)));
}
+
+// "ReadMemoryRequest": {
+// "allOf": [ { "$ref": "#/definitions/Request" },
@@ -1085,6 +1085,19 @@ std::string
VariableDescription::GetResult(llvm::StringRef context) {
return description.trim().str();
}
+lldb::addr_t GetMemoryReference(lldb::SBValue v) {
+ if (!v.GetType().IsPointerType() && !v.GetType().IsArrayType()) {
+return LLDB_INVALID_
@@ -1085,6 +1084,17 @@ std::string
VariableDescription::GetResult(llvm::StringRef context) {
return description.trim().str();
}
+std::optional GetMemoryReference(lldb::SBValue v) {
+ if (!v.GetType().IsPointerType() && !v.GetType().IsArrayType())
+return std::nullopt;
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/104317
>From a5b4f6e7e105d36b82f9de588d2705ad3d622953 Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Wed, 14 Aug 2024 11:52:40 +
Subject: [PATCH 1/7] [lldb-dap] Support inspecting memory
Adds suppor
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/102928
>From fcc6b56e27eb1bb564ccf04a328fecc5c02cf78e 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/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/102928
>From 079def868f0216f31b78469f63034db5b350e250 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/slydiman updated
https://github.com/llvm/llvm-project/pull/104238
>From 8491aa073ae240eb5e31df12ac278c70fc9515e7 Mon Sep 17 00:00:00 2001
From: Dmitry Vasilyev
Date: Fri, 16 Aug 2024 17:03:37 +0400
Subject: [PATCH 1/3] [lldb] Removed gdbserver ports map from lldb-server
List
@@ -147,15 +147,8 @@ GDB-SERVER CONNECTIONS
.. option:: --gdbserver-port
- Define a port to be used for gdb-server connections. Can be specified multiple
- times to allow multiple ports. Has no effect if --min-gdbserver-port
- and --max-gdbserver-port are specified.
-
-.. op
slydiman wrote:
@labath
> Basically, the code should look similar to
> [this](https://github.com/llvm/llvm-project/blob/f71b63865140cf3c286baf3a77ba3e467f929504/lldb/source/Host/common/TCPSocket.cpp#L267),
> except that it will be listening to two unrelated sockets.
> Reasoning about a single
https://github.com/feg208 updated
https://github.com/llvm/llvm-project/pull/104109
>From 8f2f84294ea3875c88ce36a4980fd3a3afce01de Mon Sep 17 00:00:00 2001
From: Fred Grim
Date: Tue, 18 Jun 2024 10:38:09 -0700
Subject: [PATCH 1/7] [lldb] Add Populate Methods for ELFLinuxPrPsInfo and
ELFLinuxPrS
@@ -318,6 +318,32 @@ Status ELFLinuxPrStatus::Parse(const DataExtractor &data,
return error;
}
+static struct compat_timeval
+copy_timespecs(const ProcessInstanceInfo::timespec &oth) {
+ using sec_t = decltype(compat_timeval::tv_sec);
+ using usec_t = decltype(compat_timev
https://github.com/vogelsgesang created
https://github.com/llvm/llvm-project/pull/104589
Note to reviewers: This commit builds on top of the not-yet-merged PR #102928.
When reviewing, ignore the first commit, it is part of the over PR. I will
rebase and turn this into a non-draft PR after #102
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Adrian Vogelsgesang (vogelsgesang)
Changes
Note to reviewers: This commit builds on top of the not-yet-merged PR #102928. When reviewing, ignore the first commit, it is part of the over PR.
I will rebase and turn this into a non-draft PR af
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
82ee31f75ac1316006fa9e21dddfddec37cf7072...b0fee0c0c32001064aeab1ebca209fef02c6cb98
lldb/
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 82ee31f75ac1316006fa9e21dddfddec37cf7072
b0fee0c0c32001064aeab1ebca209fef02c6cb98 --e
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/104589
>From 079def868f0216f31b78469f63034db5b350e250 Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Sat, 10 Aug 2024 23:59:55 +
Subject: [PATCH 1/2] [lldb-dap] Implement declaration locations
This
@@ -457,34 +456,24 @@ MinidumpParser::FindMemoryRange(lldb::addr_t addr) {
}
}
- // Some Minidumps have a Memory64ListStream that captures all the heap memory
- // (full-memory Minidumps). We can't exactly use the same loop as above,
- // because the Minidump uses sl
https://github.com/Jlalond updated
https://github.com/llvm/llvm-project/pull/101086
>From 2860a75fdc243f55d1e675068f9d120fb43cb21d Mon Sep 17 00:00:00 2001
From: Jacob Lalonde
Date: Fri, 26 Jul 2024 14:14:42 -0700
Subject: [PATCH 1/3] Remove 64b specific method and create Cache from both
memor
Jlalond wrote:
@labath appreciate the review, I've addressed the points. CC: @clayborg
https://github.com/llvm/llvm-project/pull/101086
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-comm
@@ -979,6 +988,8 @@ size_t StackFrameList::GetStatus(Stream &strm, uint32_t
first_frame,
++num_frames_displayed;
}
+ if (filtered)
+strm << "Note: Some frames were hidden by frame recognizers\n";
adrian-prantl wrote:
Yes, this is intentional. Fram
feg208 wrote:
The build failure here was a timeout in
```
TEST 'lldb-api ::
functionalities/fork/concurrent_vfork/TestConcurrentVFork.py' FAILED
Script:
--
/usr/bin/python3.10
/var/lib/buildkite-agent/builds/linux-56-59b8f5d88-j5dcb-1/llvm-project/gith
adrian-prantl wrote:
> ... But i do wonder if there should be a way for a user to provide regexes
> that should behave this way too.
The idea is that users can write their own frame recognizers in Python (though
I have not exposed this in this patch). I'll see if I can ad this!
> I don't know
adrian-prantl wrote:
> This seems pretty cool! Question: what would happen if the top frame (the one
> with the PC) gets filtered out by the recognizer?
The current frame never gets filtered. If you select a filtered frame with `f
123` and run `bt` the current frame will be there.
https://git
@@ -1048,6 +1048,9 @@ let Command = "thread backtrace" in {
Arg<"FrameIndex">, Desc<"Frame in which to start the backtrace">;
def thread_backtrace_extended : Option<"extended", "e">, Group<1>,
Arg<"Boolean">, Desc<"Show the extended backtrace, if available">;
+ def threa
adrian-prantl wrote:
Action items so far:
- change the option to `--unfiltered` (no argument)
- expose in SBFrame
- expose in Python
https://github.com/llvm/llvm-project/pull/104523
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://list
feg208 wrote:
Added issue https://github.com/llvm/llvm-project/issues/104609 to track the
timeout
https://github.com/llvm/llvm-project/pull/104109
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinf
Author: Fred Grim
Date: 2024-08-16T08:53:15-07:00
New Revision: a434cac523da6db542350fd747967520aaae8fbb
URL:
https://github.com/llvm/llvm-project/commit/a434cac523da6db542350fd747967520aaae8fbb
DIFF:
https://github.com/llvm/llvm-project/commit/a434cac523da6db542350fd747967520aaae8fbb.diff
LOG
https://github.com/feg208 closed
https://github.com/llvm/llvm-project/pull/104109
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-x86_64-debian`
running on `lldb-x86_64-debian` while building `lldb` at step 6 "test".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/162/builds/4235
Here is the relevant piece of the build log f
vogelsgesang wrote:
Should hidden frames also be skipped by `StepOut`?
https://github.com/llvm/llvm-project/pull/104523
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/feg208 created
https://github.com/llvm/llvm-project/pull/104617
In implementing this test one of the assertions assumes that the priority is
the default in linux (0) but, evidently, some of the build runners prioritize
the test to, at least, 5. This ensures that regardless o
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Fred Grim (feg208)
Changes
In implementing this test one of the assertions assumes that the priority is
the default in linux (0) but, evidently, some of the build runners prioritize
the test to, at least, 5. This ensures that regardless of
kendalharland wrote:
> Can those swift libraries be found automatically? For example if they're at
> some known path relative to lldb or the swift compiler?
Yes. They can be copied into the python module where _lldb resides. Help me
understand: why is this preferrable over an explicit input t
kendalharland wrote:
Actually, @labath I missed the last suggestion in
https://github.com/llvm/llvm-project/issues/46235 which says this can be done
by modifying bindings/python.swig. That sounds like something that I can do in
Swift's fork? Maybe I'll see if that works.
https://github.com/ll
https://github.com/jeffreytan81 edited
https://github.com/llvm/llvm-project/pull/104532
___
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/104532
>From e86454235bf3bd20be1ddc394683d3f475fad218 Mon Sep 17 00:00:00 2001
From: jeffreytan81
Date: Thu, 15 Aug 2024 18:12:04 -0700
Subject: [PATCH 1/2] Fix async interrupt for step over breakpoint
---
lldb/
https://github.com/jeffreytan81 edited
https://github.com/llvm/llvm-project/pull/104532
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
jimingham wrote:
When we were talking about this originally I thought that StackFrames would get
an "ImplementationFrame" property, and we would use that to determine whether
to hide the frame in bt (when not passing --unfiltered). Then the frame
recognizers when they are run on the frame in
jimingham wrote:
BTW, we should definitely get StepOut to step out past hidden frames. That
should be pretty easy to do.
https://github.com/llvm/llvm-project/pull/104523
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org
@@ -174,6 +176,82 @@ struct StatisticsOptions {
std::optional m_include_transcript;
};
+/// A class that represents statistics about a TypeSummaryProviders invocations
+class SummaryStatistics {
+public:
+ explicit SummaryStatistics(std::string name, std::string impl_type)
ilovepi wrote:
We're seeing a failure in our CI after this patch, would you mind taking a look
and reverting if its going to take a while to fix?
Error:
```
FAILED:
tools/lldb/unittests/Process/elf-core/CMakeFiles/ProcessElfCoreTests.dir/ThreadElfCoreTest.cpp.o
/b/s/w/ir/x/w/rc/cxx-rbe47grl
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/102185
>From e40ca68a934d0595ebc6c07010a4f6a814fa026f Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Sat, 27 Jul 2024 02:39:32 +0200
Subject: [PATCH] [lldb][test] Improve toolchain detection in Makefile.r
dzhidzhoev wrote:
Updated added dwp tool handling, to adopt changes from
e77ac42bccb8c26bbf4b74d8e92eb09e7fa1b218 and resolve merge conflict.
https://github.com/llvm/llvm-project/pull/102185
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
ht
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/102185
>From e40ca68a934d0595ebc6c07010a4f6a814fa026f Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Sat, 27 Jul 2024 02:39:32 +0200
Subject: [PATCH 1/2] [lldb][test] Improve toolchain detection in
Makef
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/95986
>From 8be2b2fece5291bf57d493464839d6a7cc999db1 Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Fri, 31 May 2024 21:39:56 +
Subject: [PATCH 1/6] [lldb][test] Support remote run of Shell tests
1.
@@ -165,6 +235,14 @@ def use_support_substitutions(config):
if config.cmake_sysroot:
host_flags += ["--sysroot={}".format(config.cmake_sysroot)]
+if config.enable_remote and config.has_libcxx:
+host_flags += [
+"-L{}".format(config.libcxx_li
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/95986
>From 8be2b2fece5291bf57d493464839d6a7cc999db1 Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Fri, 31 May 2024 21:39:56 +
Subject: [PATCH 1/7] [lldb][test] Support remote run of Shell tests
1.
@@ -244,6 +244,7 @@ llvm_canonicalize_cmake_booleans(
LLVM_ENABLE_ZLIB
LLVM_ENABLE_SHARED_LIBS
LLDB_HAS_LIBCXX
+ LLDB_SHELL_TESTS_DISABLE_REMOTE
dzhidzhoev wrote:
Done
https://github.com/llvm/llvm-project/pull/95986
walter-erquinigo wrote:
could you share a screenshot or something like that? :)
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/jeffreytan81 edited
https://github.com/llvm/llvm-project/pull/104532
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
1 - 100 of 107 matches
Mail list logo
