[Lldb-commits] [lldb] r330385 - [DWARFASTParserClang] Remove dead code. NFCI.

2018-04-19 Thread Davide Italiano via lldb-commits
Author: davide Date: Thu Apr 19 17:44:33 2018 New Revision: 330385 URL: http://llvm.org/viewvc/llvm-project?rev=330385=rev Log: [DWARFASTParserClang] Remove dead code. NFCI. Modified: lldb/trunk/source/Plugins/SymbolFile/DWARF/DWARFASTParserClang.cpp Modified:

Re: [Lldb-commits] [lldb] r330314 - Attempt to fix TestMiniDump on windows

2018-04-19 Thread Leonard Mosescu via lldb-commits
The mix of backward and forward slashes doesn't impact my current project but it would be nice to have a consistent path syntax (both within a single path and also cross platforms). > Leonard, is it reasonable to assume that all paths in the minidumps will be > absolute (and thus resolving is

[Lldb-commits] [PATCH] D45700: Improve LLDB's handling of non-local minidumps

2018-04-19 Thread Leonard Mosescu via Phabricator via lldb-commits
lemo added subscribers: bgianfo, penryu. lemo added a comment. > It looks like nobody except me is worried about the > module-without-an-object-file situation, so I guess we can try this out and > see how it goes. Sorry Pavel, I meant to respond to this: most of the code seems to explicitly

Re: [Lldb-commits] [PATCH] D45700: Improve LLDB's handling of non-local minidumps

2018-04-19 Thread Leonard Mosescu via lldb-commits
> > It looks like nobody except me is worried about the > module-without-an-object-file situation, so I guess we can try this out and > see how it goes. > Sorry Pavel, I meant to respond to this: most of the code seems to explicitly handle this case (module-without-object-file), I just had to fix

Re: [Lldb-commits] [lldb] r330314 - Attempt to fix TestMiniDump on windows

2018-04-19 Thread Pavel Labath via lldb-commits
Yes, I noticed that as well, but I did not want to change it, as it wasn't related to the problem I was trying to fix. I agree that not resolving the path sounds like a better idea. Leonard, is it reasonable to assume that all paths in the minidumps will be absolute (and thus resolving is

Re: [Lldb-commits] [lldb] r330314 - Attempt to fix TestMiniDump on windows

2018-04-19 Thread Greg Clayton via lldb-commits
Any reason we are trying to resolve the path with the 2nd true argument to FileSpec? If you still want to resolve the path, I would suggest checking if GetArchitecture() is compatible with any host architectures before passing true. > On Apr 19, 2018, at 2:38 AM, Pavel Labath via lldb-commits

[Lldb-commits] [PATCH] D45700: Improve LLDB's handling of non-local minidumps

2018-04-19 Thread Pavel Labath via Phabricator via lldb-commits
labath added a comment. It looks like nobody except me is worried about the module-without-an-object-file situation, so I guess we can try this out and see how it goes. The test you've added here has been failing on windows though. I've tried to fix this in r330314, but it meant modifying the

[Lldb-commits] [lldb] r330314 - Attempt to fix TestMiniDump on windows

2018-04-19 Thread Pavel Labath via lldb-commits
Author: labath Date: Thu Apr 19 02:38:42 2018 New Revision: 330314 URL: http://llvm.org/viewvc/llvm-project?rev=330314=rev Log: 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)