Pavel Labath acebc43799 Report more precise error message when attach fails ... Summary: If the remote stub sends a specific error message instead of just a E?? code, we can use this to display a more informative error message instead of just the generic "unable to attach" message. I write a test for this using the SB API. On the console this will show up like: (lldb) process attach ... error: attach failed: <STUB-MESSAGE> if the stub supports error messages, or: error: attach failed: Error ?? if it doesn't. Reviewers: jingham, JDevlieghere Subscribers: lldb-commits Differential Revision: https://reviews.llvm.org/D45573 llvm-svn: 330247		2018-04-18 11:56:21 +00:00
..
a.yaml
gdbclientutils.py	Report more precise error message when attach fails	2018-04-18 11:56:21 +00:00
operating_system.py	Re-land "Don't assume backing thread shares protocol ID."	2018-04-13 11:31:34 +00:00
TestGDBRemoteClient.py	Report more precise error message when attach fails	2018-04-18 11:56:21 +00:00
TestGDBRemoteLoad.py	Add a test for setting the load address of a module with differing physical/virtual addresses	2018-03-26 11:45:32 +00:00
TestRestartBug.py	Rewrite the flaky test_restart_bug test in a more deterministic way	2018-02-08 10:37:23 +00:00
TestTargetXMLArch.py	[LLDB] Fix TestTargetXMLArch's expected arch	2018-03-20 13:46:05 +00:00
TestThreadSelectionBug.py	Re-land "Don't assume backing thread shares protocol ID."	2018-04-13 11:31:34 +00:00