Skip to content
  1. Oct 20, 2010
  2. Oct 19, 2010
  3. Oct 18, 2010
  4. Oct 09, 2010
  5. Oct 08, 2010
  6. Oct 06, 2010
  7. Sep 27, 2010
  8. Sep 20, 2010
  9. Sep 19, 2010
  10. Sep 16, 2010
    • Johnny Chen's avatar
      Added a test case for the settings command which sets process.output-path and · 2fcc0e55
      Johnny Chen authored
      checks that the launched process writes its standard output there.
      
      llvm-svn: 114102
      2fcc0e55
    • Johnny Chen's avatar
      Provided a mechanism for the test class to cleanup after itself once it's done. · 1a9f4dd5
      Johnny Chen authored
      This will remove the confusion experienced when previous test runs left some
      files (both intermediate or by-product as a result of the test).
      
      lldbtest.TestBase defines a classmethod tearDownClass(cls) which invokes the
      platform-specific cleanup() function as defined by the plugin; after that, it
      invokes a subclass-specific function classCleanup(cls) if defined; and, finally,
      it restores the old working directory.
      
      An example of classCleanup(cls) is in settings/TestSettings.py:
      
          @classmethod
          def classCleanup(cls):
              system(["/bin/sh", "-c", "rm output.txt"])
      
      where it deletes the by-product "output.txt" as a result of running a.out.
      
      llvm-svn: 114058
      1a9f4dd5
    • Johnny Chen's avatar
      Added two test cases to TestSettings.py which exercise the lldb's: · d5e111c2
      Johnny Chen authored
      (lldb) settings set process.run-args A B C
      (lldb) settings set process.env-vars ["MY_ENV_VAR"]=YES
      
      commands.  The main.cpp checks whether A, B, C is passed to main and whether
      the $MY_ENV_VAR env variable is defined and outputs the findings to a file.
      
      llvm-svn: 114031
      d5e111c2
  11. Sep 07, 2010
Loading