================
@@ -186,3 +186,28 @@ def
test_jAcceleratorPluginBreakpointHit_returns_connect_info(self):
connect_info["connect_url"],
)
self.assertTrue(connect_info["synchronous"])
+
+ @add_test_categories(["llgs"])
+ def test_jAcceleratorPluginGetDynamicLoaderLibraryInfo(self):
+ self.build()
+ self.set_inferior_startup_launch()
+ self.prep_debug_monitor_and_inferior()
+
+ self.add_qSupported_packets()
+ self.expect_gdbremote_sequence()
+
+ dyld_args = {"plugin_name": "mock", "full": True}
----------------
DavidSpickett wrote:
Is it correct to say here that we could implement full=False in the mock plugin
but it wouldn't help us test anything but the mock plugin itself at this stage?
Testing different values of full is best done with real plugins later, since
it's all up to the plugin to handle it.
https://github.com/llvm/llvm-project/pull/214564
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
