Lines Matching full:command
52 This command will cause you to be prompted to enter the command or set of\n\
54 will be told to enter your command(s), and will see a '> 'prompt. Because\n\
61 An improperly written breakpoint command will attempt to get executed when the\n\
62 breakpoint gets hit, and usually silently fail. If your breakpoint command does\n\
73 you finish entering the breakpoint command, and they can be called later (don't\n\
115 Example Python one-line breakpoint command:\n\
117 (lldb) breakpoint command add -s python 1\n\
118 Enter your Python command(s). Type 'DONE' to end.\n\
123 (lldb) breakpoint command add -s python 1 -o \"import time; print time.asctime()\"\n\
138 Example multiple line Python breakpoint command, using function definition:\n\
140 (lldb) breakpoint command add -s python 1\n\
141 Enter your Python command(s). Type 'DONE' to end.\n\
150 Example multiple line Python breakpoint command, using 'loose' Python:\n\
152 (lldb) breakpoint command add -s p 1\n\
153 Enter your Python command(s). Type 'DONE' to end.\n\
176 Final Note: If you get a warning that no breakpoint command was generated, but\n\
180 Special information about debugger command breakpoint commands\n\
183 You may enter any debugger command, exactly as you would at the debugger prompt.\n\
185 one command per line.\n" );
254 // The former is used to generate callback description (as in breakpoint command list)
322 // Finish, and cancel the breakpoint command.
336 out_stream->Printf ("Warning: No command attached to breakpoint.\n");
494 // Instance variables to hold the values for command options.
509 DoExecute (Args& command, CommandReturnObject &result)
532 result.AppendError ("need to enable scripting to have a function run as a breakpoint command");
538 CommandObjectMultiwordBreakpoint::VerifyBreakpointIDs (command, target, result, &valid_bp_ids);
575 // in order to set or collect command callback. Otherwise, call
587 // what the user would do manually: make their breakpoint command be a function call
626 CommandObjectBreakpointCommandAdd::g_reader_instructions = "Enter your debugger command(s). Type 'DONE' to end.";
634 { eScriptLanguageNone, "command", "Commands are in the lldb command interpreter language"},
644 "Specify a one-line breakpoint command inline. Be sure to surround it with quotes." },
647 "Specify whether breakpoint command execution should terminate on error." },
650 "Specify the language for the commands - if none is specified, the lldb command interpreter will be used."},
653 "Give the name of a Python function to run as command for this breakpoint. Be sure to give a module name if appropriate."},
691 DoExecute (Args& command, CommandReturnObject &result)
712 if (command.GetArgumentCount() == 0)
720 CommandObjectMultiwordBreakpoint::VerifyBreakpointIDs (command, target, result, &valid_bp_ids);
788 DoExecute (Args& command,
810 if (command.GetArgumentCount() == 0)
818 CommandObjectMultiwordBreakpoint::VerifyBreakpointIDs (command
868 result.AppendMessageWithFormat ("Breakpoint %s does not have an associated command.\n",
894 "command",
896 "command <sub-command> [<sub-command-options>] <breakpoint-id>")
902 add_command_object->SetCommandName ("breakpoint command add");
903 delete_command_object->SetCommandName ("breakpoint command delete");
904 list_command_object->SetCommandName ("breakpoint command list");
