Fix Arg0 argument after r229110. The problem was that Arg0ValueChangedCallback isn't twitching when Arg0 was updated, therefore target was launched with empty 1st argument or without it at all. In this patch I update Arg0 by hand.

llvm-svn: 229125
This commit is contained in:
Ilia K 2015-02-13 17:07:55 +00:00
parent 30d471f6aa
commit cc39d3f4bd
3 changed files with 4 additions and 3 deletions

View File

@ -201,7 +201,7 @@ public:
SetDisplayRuntimeSupportValues (bool b);
const ProcessLaunchInfo &
GetProcessLaunchInfo() const;
GetProcessLaunchInfo();
void
SetProcessLaunchInfo(const ProcessLaunchInfo &launch_info);

View File

@ -249,7 +249,7 @@ protected:
if (launch_args.GetArgumentCount() == 0)
{
m_options.launch_info.GetArguments() = target->GetProcessLaunchInfo().GetArguments();
m_options.launch_info.GetArguments().AppendArguments (target->GetProcessLaunchInfo().GetArguments());
}
else
{

View File

@ -3407,8 +3407,9 @@ TargetProperties::SetDisplayRuntimeSupportValues (bool b)
}
const ProcessLaunchInfo &
TargetProperties::GetProcessLaunchInfo () const
TargetProperties::GetProcessLaunchInfo ()
{
m_launch_info.SetArg0(GetArg0()); // FIXME: Arg0 callback doesn't work
return m_launch_info;
}