https://github.com/slydiman edited
https://github.com/llvm/llvm-project/pull/99721
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/medismailben updated
https://github.com/llvm/llvm-project/pull/97273
>From 16ef7297eef25d329631fd62d126bf7a7be24c4d Mon Sep 17 00:00:00 2001
From: Med Ismail Bennani
Date: Fri, 19 Jul 2024 11:08:39 -0700
Subject: [PATCH 1/2] [lldb/Target] Add GetStartSymbol method to DynamicL
https://github.com/slydiman updated
https://github.com/llvm/llvm-project/pull/99721
>From c033ba3832141409c2dac7e7363c0c85caa2274b Mon Sep 17 00:00:00 2001
From: Dmitry Vasilyev
Date: Sat, 20 Jul 2024 03:48:12 +0400
Subject: [PATCH] [lldb][Windows] Fixed Host::Kill()
HostProcessWindows::Termin
https://github.com/slydiman edited
https://github.com/llvm/llvm-project/pull/99721
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
walter-erquinigo wrote:
This is very exciting!
https://github.com/llvm/llvm-project/pull/99736
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
rocallahan wrote:
> I've noticed you didn't check if this works both when the debugger is in
> synchronous and asynchronous in your tests.
OK, I've added this.
> I'm not sure what additional information does the History Boundary stop
> reason provides. Can it actually provide historical data
@@ -1395,6 +1395,91 @@ Status ProcessGDBRemote::DoResume() {
return error;
}
+Status ProcessGDBRemote::DoResumeReverse() {
+ Status error;
+ Log *log = GetLog(GDBRLog::Process);
+ LLDB_LOGF(log, "ProcessGDBRemote::DoResumeReverse()");
+
+ ListenerSP listener_sp(
+ L
@@ -0,0 +1,79 @@
+import lldb
+import unittest
+from lldbsuite.test.lldbtest import *
+from lldbsuite.test.decorators import *
+from lldbsuite.test.gdbclientutils import *
+from lldbsuite.test.lldbreverse import ReverseTestBase
+from lldbsuite.test import lldbutil
+
+
+class TestR
@@ -0,0 +1,79 @@
+import lldb
+import unittest
+from lldbsuite.test.lldbtest import *
+from lldbsuite.test.decorators import *
+from lldbsuite.test.gdbclientutils import *
+from lldbsuite.test.lldbreverse import ReverseTestBase
+from lldbsuite.test import lldbutil
+
+
+class TestR
@@ -0,0 +1,12 @@
+static void start_recording() {}
+
+static void trigger_breakpoint() {}
+
+static void stop_recording() {}
rocallahan wrote:
None of that functionality interacts with reverse execution, so I don't think
we need to test it in combination with re
@@ -0,0 +1,79 @@
+import lldb
+import unittest
+from lldbsuite.test.lldbtest import *
+from lldbsuite.test.decorators import *
+from lldbsuite.test.gdbclientutils import *
+from lldbsuite.test.lldbreverse import ReverseTestBase
+from lldbsuite.test import lldbutil
+
+
+class TestR
@@ -1881,18 +1970,24 @@ ThreadSP ProcessGDBRemote::SetThreadStopInfo(
handled = true;
}
} else if (!signo) {
-addr_t pc = thread_sp->GetRegisterContext()->GetPC();
-lldb::BreakpointSiteSP bp_site_sp =
-thread_sp->GetProcess()-
@@ -1881,18 +1970,24 @@ ThreadSP ProcessGDBRemote::SetThreadStopInfo(
handled = true;
}
} else if (!signo) {
-addr_t pc = thread_sp->GetRegisterContext()->GetPC();
-lldb::BreakpointSiteSP bp_site_sp =
-thread_sp->GetProcess()-
https://github.com/rocallahan updated
https://github.com/llvm/llvm-project/pull/99736
>From 25e184d1f0d06c09726ef72c0b3f1966522ea3df Mon Sep 17 00:00:00 2001
From: Robert O'Callahan
Date: Fri, 19 Jul 2024 22:46:42 +1200
Subject: [PATCH] [lldb] Implement basic support for reverse-continue
This
mstorsjo wrote:
FYI, I also ran into failures due to this change, when debugging on Windows
(with DWARF). See the run in
https://github.com/mstorsjo/actions-test/actions/runs/10020326811 vs
https://github.com/mstorsjo/actions-test/actions/runs/10020393197. Thanks for
reverting; hopefully it’s
jasonmolenda wrote:
> FYI, I also ran into failures due to this change, when debugging on Windows
> (with DWARF). See the run in
> https://github.com/mstorsjo/actions-test/actions/runs/10020326811 vs
> https://github.com/mstorsjo/actions-test/actions/runs/10020393197. Thanks for
> reverting;
mstorsjo wrote:
> > FYI, I also ran into failures due to this change, when debugging on Windows
> > (with DWARF). See the run in
> > https://github.com/mstorsjo/actions-test/actions/runs/10020326811 vs
> > https://github.com/mstorsjo/actions-test/actions/runs/10020393197. Thanks
> > for rever
jasonmolenda wrote:
I haven't tested it (or even tried to compile it, lol) but I think this loop
might be expressable as simply
```
MemoryRegionInfo region_info;
while (process_sp->GetMemoryRegionInfo(ret, region_info) == err.Success() &&
region_info.GetRange().GetRangeEnd() - 1
jasonmolenda wrote:
Ah, but I see my misunderstanding as I look at what debugserver returns. It
uses "no permissions" to indicate a memory range that is unmapped --
```
< 23> send packet: $qMemoryRegionInfo:0#44
< 27> read packet: $start:0;size:1;#00
< 31> send packet: $qMemoryR
https://github.com/JDevlieghere approved this pull request.
Neat
https://github.com/llvm/llvm-project/pull/99721
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
20 matches
Mail list logo
