[Lldb-commits] [PATCH] D40475: DWZ 12/12: DWZ test mode

[Jim Ingham via lldb-commits]

We had a similar problem with the tests on macOS.  lldb has a facility that will do automatic lookup of UUID -> dSYM (macOS's separate debug info format) and if you are internal to Apple this will find all the system library debug info.  That will cause a handful of tests to fail, mostly because the presence of debug information changes stepping behavior.  doTest.py has a method: "checkDsymForUUIDIsNotOn" to ensure that this facility is turned off and if it is not will warn you and abort the test run.

You are going to have to do something of that sort even once you get reading these libraries in to work, so I agree a setting seems like a good idea.  There is a setting for debug file search paths: target.debug-file-search-paths but I'd rather not add a special cookie to that since you can imagine wanting to point to a directory with your debug info and ALSO not read in the system debug info.  So it would be better IMO to add a parallel debug-file-avoid-directory setting.  

Jim
 

> On Nov 30, 2017, at 6:57 AM, Pavel Labath via Phabricator via lldb-commits <lldb-commits at lists.llvm.org> wrote:
> 
>> BTW with installed system debug info files (`/usr/lib/debug/**.debug`) the LLDB testsuite times out and fails completely.  LLDB could have some option like: `gdb -iex 'set debug-file-directory /notexists'`
> 
> Yea, that would be useful, particularly as we want to isolate the test from system specifics. It would also be useful to figure out why does it hang, as it will probably affect your users as well. :)
>