From f7e07256283cc080b2720ee6587b96d92ef6f9e5 Mon Sep 17 00:00:00 2001 From: Jim Ingham Date: Mon, 26 Sep 2016 19:47:37 +0000 Subject: Fix serialization of Python breakpoint commands. CommandData breakpoint commands didn't know whether they were Python or Command line commands, so they couldn't serialize & deserialize themselves properly. Fix that. I also changed the "breakpoint list" command to note in the output when the commands are Python commands. Fortunately only one test was relying on this explicit bit of text output. llvm-svn: 282432 --- lldb/source/Commands/CommandObjectBreakpointCommand.cpp | 7 ------- 1 file changed, 7 deletions(-) (limited to 'lldb/source/Commands/CommandObjectBreakpointCommand.cpp') diff --git a/lldb/source/Commands/CommandObjectBreakpointCommand.cpp b/lldb/source/Commands/CommandObjectBreakpointCommand.cpp index f27fb7cf7bdb..1d2d6a1dd2b6 100644 --- a/lldb/source/Commands/CommandObjectBreakpointCommand.cpp +++ b/lldb/source/Commands/CommandObjectBreakpointCommand.cpp @@ -264,14 +264,7 @@ are no syntax errors may indicate that a function was declared but never called. for (auto bp_options : bp_options_vec) { auto cmd_data = llvm::make_unique(); - // It's necessary to set both user_source and script_source to the - // oneliner. - // The former is used to generate callback description (as in breakpoint - // command list) - // while the latter is used for Python to interpret during the actual - // callback. cmd_data->user_source.AppendString(oneliner); - cmd_data->script_source.assign(oneliner); cmd_data->stop_on_error = m_options.m_stop_on_error; bp_options->SetCommandDataCallback(cmd_data); -- cgit v1.2.3