Pavel Labath 5976f30821 Attempt to fix TestMiniDump on windows ... It was failing because the modules names were coming out as C:\Windows\System32/MSVCP120D.dll (last separator is a forward slash) on windows. There are two issues at play here: - the first problem is that the paths in minidump were being parsed as a host path. This meant that on posix systems the whole path was interpreted as a file name. - on windows the path was split into a directory-filename pair correctly, but then when it was reconsituted, the last separator ended up being a forward slash because SBFileSpec.fullpath was joining them with '/' unconditionally. I fix the first issue by parsing the minidump paths according to the path syntax of the host which produced the dump, which should make the test behavior on posix&windows identical. The last path will still be a forward slash because of the second issue. We should probably fix the "fullpath" property to do something smarter in the future. llvm-svn: 330314		2018-04-19 09:38:42 +00:00
..
elf-core	Last batch of test-tree cleaning changes	2018-03-21 15:29:32 +00:00
mach-core	[test] Disable TestMachCore everywhere except on Darwin	2018-03-14 14:16:23 +00:00
minidump	Attempt to fix TestMiniDump on windows	2018-04-19 09:38:42 +00:00
minidump-new	Improve LLDB's handling of non-local minidumps	2018-04-18 23:10:46 +00:00
wow64_minidump	Disable windows-only minidump plugin	2016-11-09 10:16:11 +00:00