Marc-Andre Laperle b71a94f4f2 LLDB: Print an error when lldb is below minimum version ... Prevent users from using a version of lldb that is too old. Before version 3.8 there was a hang and other issues. If the version cannot be determined, the launch stil proceeds. This is because there is no good way to get the version from the lldb-mi executable but rather, we can only do a best-effort to get the version from the normal lldb executable. If the lldb executable is not present but the lldb-mi is, this is a valid way to use the debugger but the version cannot be determined. In the future, it would be better if the lldb-mi executable could report the lldb version directly. But this would be an improvement in lldb, not CDT. Change-Id: Ief8a4ebd3ea1e3d549a5cef41ac3030ec48734c4 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> (cherry picked from commit e5d8f677b2)		2016-08-28 11:18:19 -04:00
..
org.eclipse.cdt.llvm.dsf.lldb-feature	Fix outdated pom versions in lldb folders	2016-08-19 12:27:23 -04:00
org.eclipse.cdt.llvm.dsf.lldb.core	LLDB: Print an error when lldb is below minimum version	2016-08-28 11:18:19 -04:00
org.eclipse.cdt.llvm.dsf.lldb.ui	Fix outdated pom versions in lldb folders	2016-08-19 12:27:23 -04:00
org.eclipse.cdt.managedbuilder.llvm-feature	Update version to 9.1.0	2016-08-17 10:11:57 -04:00
org.eclipse.cdt.managedbuilder.llvm.tests	Move the rest of the CDT plugins to java 8	2016-06-22 14:51:43 -04:00
org.eclipse.cdt.managedbuilder.llvm.ui	Update version to 9.1.0	2016-08-17 10:11:57 -04:00