fix-tests
Demonstrate how to use the config file and the pre-flight functionality to route the lldb gdb-remote log messages into individually named log destinations. In the simple usage-lldb-loggings example, we ran two cases which resulted in two lldb_log files.
[lldb] Remove LLDB session dir and just store test traces in the respective test build directory
Add the capability of supplying the pre/post-flight functions to the test suite such that the pre-flight code gets executed during setUp() after the debugger instance is available and the post-flight code gets executed during tearDown() after the debugger instance has done killing the inferior and deleting all the target programs.
Added the capability for the test driver to split the sys.stderr/sys.stdout into different configuration-based files using the config file. For example:
Add comment explaining the options used to invoke the test driver.
Added the capability to source the configFile specified via the "-c" option in order to customize the running of the test suite. For the time being, the supported customizations are: