5 Commits

Author	SHA1	Message	Date
Johnny Chen	93b0c8b2aa	Remove the expectedFailure decorator for the fixed bug: ... rdar://problem/8435794 settings set target.process.output-path does not seem to work Also change the test case from test_set_output_path to test_set_error_output_path as it now exercises both setting target.process.error-path and target.process.output-path. llvm-svn: 124198	2011-01-25 17:39:43 +00:00
Johnny Chen	a245f933ba	Make the TestSettings.py test cases use different output filenames: ... o "output1.txt" for test_pass_host_env_vars() test case o "output2.txt" for test_run_args_and_env_vars_with_dsym() test case o "output2.txt" for test_run_args_and_env_vars_with_dwarf() test case and add teardown hook to test_pass_host_env_vars() in order to properly unset the host environment variables set while running the test case. llvm-svn: 121811	2010-12-14 23:43:29 +00:00
Johnny Chen	80554b804d	Add a test method test_pass_host_env_vars to 'class SettingsCommandTestCase(TestBase)' ... which tests the recently added lldb feature of automatically passing the host environment variables to the launched process. llvm-svn: 120871	2010-12-04 00:44:56 +00:00
Johnny Chen	f7f627104b	Simplied main() and emits a message to the standard out. ... llvm-svn: 114033	2010-09-15 22:48:40 +00:00
Johnny Chen	d5e111c2c1	Added two test cases to TestSettings.py which exercise the lldb's: ... (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	2010-09-15 22:27:29 +00:00