aboutsummaryrefslogtreecommitdiff
path: root/lldb/test/API/python_api
diff options
context:
space:
mode:
authorBruce Mitchener <bruce.mitchener@gmail.com>2021-06-05 15:50:49 +0700
committerBruce Mitchener <bruce.mitchener@gmail.com>2021-06-05 15:50:49 +0700
commit2606918f467519f1634a67ee386211e99665fd23 (patch)
tree08ea621594e008b68279e3ea0c18f113ff33d813 /lldb/test/API/python_api
parentdb45746821ab01a54f8df033991c3280c4284e3b (diff)
downloadllvm-2606918f467519f1634a67ee386211e99665fd23.zip
llvm-2606918f467519f1634a67ee386211e99665fd23.tar.gz
llvm-2606918f467519f1634a67ee386211e99665fd23.tar.bz2
Revert "[LLDB/API] Expose args and env from SBProcessInfo."
This reverts commit 8d33437d030af27fff21dd3fd0e66893b0148217. This broke one of the buildbots.
Diffstat (limited to 'lldb/test/API/python_api')
-rw-r--r--lldb/test/API/python_api/process/TestProcessAPI.py7
1 files changed, 0 insertions, 7 deletions
diff --git a/lldb/test/API/python_api/process/TestProcessAPI.py b/lldb/test/API/python_api/process/TestProcessAPI.py
index 5df9eb9..b7efc7e 100644
--- a/lldb/test/API/python_api/process/TestProcessAPI.py
+++ b/lldb/test/API/python_api/process/TestProcessAPI.py
@@ -335,8 +335,6 @@ class ProcessAPITestCase(TestBase):
# Launch the process and stop at the entry point.
launch_info = target.GetLaunchInfo()
launch_info.SetWorkingDirectory(self.get_process_working_directory())
- launch_info.SetEnvironmentEntries(["FOO=BAR"], False)
- launch_info.SetArguments(["--abc"], False)
launch_flags = launch_info.GetLaunchFlags()
launch_flags |= lldb.eLaunchFlagStopAtEntry
launch_info.SetLaunchFlags(launch_flags)
@@ -360,11 +358,6 @@ class ProcessAPITestCase(TestBase):
"Process ID is valid")
triple = process_info.GetTriple()
self.assertIsNotNone(triple, "Process has a triple")
- env = process_info.GetEnvironment()
- self.assertGreater(env.GetNumValues(), 0)
- self.assertEqual("BAR", env.Get("FOO"))
- self.assertEqual(process_info.GetNumArguments(), 1)
- self.assertEqual("--abc", process_info.GetArgumentAtIndex(0))
# Additional process info varies by platform, so just check that
# whatever info was retrieved is consistent and nothing blows up.