From 0161b49cbadd54431b4acefa8dae954ebef12ec8 Mon Sep 17 00:00:00 2001 From: Jim Ingham Date: Sat, 9 Feb 2013 01:29:05 +0000 Subject: Reworked the way Process::RunThreadPlan and the ThreadPlanCallFunction interoperate to fix problems where hitting auto-continue signals while running a thread plan would cause us to lose control of the debug session. llvm-svn: 174793 --- lldb/source/Commands/CommandObjectProcess.cpp | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'lldb/source/Commands/CommandObjectProcess.cpp') diff --git a/lldb/source/Commands/CommandObjectProcess.cpp b/lldb/source/Commands/CommandObjectProcess.cpp index df5d8ff9687b..f39c3227a07d 100644 --- a/lldb/source/Commands/CommandObjectProcess.cpp +++ b/lldb/source/Commands/CommandObjectProcess.cpp @@ -199,6 +199,11 @@ protected: if (environment.GetArgumentCount() > 0) m_options.launch_info.GetEnvironmentEntries ().AppendArguments (environment); + // Get the value of synchronous execution here. If you wait till after you have started to + // run, then you could have hit a breakpoint, whose command might switch the value, and + // then you'll pick up that incorrect value. + bool synchronous_execution = m_interpreter.GetSynchronous (); + // Finalize the file actions, and if none were given, default to opening // up a pseudo terminal const bool default_to_use_pty = true; @@ -258,7 +263,6 @@ protected: error = process->Resume(); if (error.Success()) { - bool synchronous_execution = m_interpreter.GetSynchronous (); if (synchronous_execution) { state = process->WaitForProcessToStop (NULL); -- cgit v1.2.3