From 3630a92dd7470ee125e5b59dc16c977c2d76a858 Mon Sep 17 00:00:00 2001 From: Vladimir Prus Date: Wed, 18 Nov 2009 20:42:38 +0000 Subject: * cli/cli-script.c (process_next_line): Recognize 'end' even when the line has leading space and we're not parsing commands. --- gdb/cli/cli-script.c | 25 +++++++++++++++---------- 1 file changed, 15 insertions(+), 10 deletions(-) (limited to 'gdb/cli') diff --git a/gdb/cli/cli-script.c b/gdb/cli/cli-script.c index 6e90bf2..0f8f393 100644 --- a/gdb/cli/cli-script.c +++ b/gdb/cli/cli-script.c @@ -879,30 +879,35 @@ static enum misc_command_type process_next_line (char *p, struct command_line **command, int parse_commands) { char *p1; + char *p2; int not_handled = 0; /* Not sure what to do here. */ if (p == NULL) return end_command; - if (parse_commands) - { - /* Strip leading whitespace. */ - while (*p == ' ' || *p == '\t') - p++; - } - /* Strip trailing whitespace. */ p1 = p + strlen (p); while (p1 != p && (p1[-1] == ' ' || p1[-1] == '\t')) p1--; - /* Is this the end of a simple, while, or if control structure? */ - if (p1 - p == 3 && !strncmp (p, "end", 3)) - return end_command; + p2 = p; + /* Strip leading whitespace. */ + while (*p2 == ' ' || *p2 == '\t') + p2++; + /* 'end' is always recognized, regardless of parse_commands value. + We also permit whitespace before end and after. */ + if (p1 - p2 == 3 && !strncmp (p2, "end", 3)) + return end_command; + if (parse_commands) { + /* If commands are parsed, we skip initial spaces. Otherwise, + which is the case for Python commands and documentation + (see the 'document' command), spaces are preserved. */ + p = p2; + /* Blanks and comments don't really do anything, but we need to distinguish them from else, end and other commands which can be executed. */ -- cgit v1.1