From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb@sourceware.org, gdb-patches@sourceware.org
Subject: [patch] Fix crash on CLI indented comments [Re: [Bug:cli] Loading user-defined function generates an internal error]
Date: Fri, 01 Jan 2010 08:41:00 -0000 [thread overview]
Message-ID: <20100101084028.GA29969@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <19259.54163.166299.854635@totara.tehura.co.nz>
On Wed, 30 Dec 2009 23:26:27 +0100, Nick Roberts wrote:
> Heres a simpler user defined function that gives a segmentation fault. It
> appears that GDB can no longer handle indented comments.
>
> define my_fun
> #indented comment
> end
(*command)->line = savestring (p, p1 - p);
#1 0x0000000000487405 in savestring (ptr=0x1d5dd31 "", size=18446744073709551615) at utils.c:1377
(gdb) p/x size
$1 = 0xffffffffffffffff
(gdb) p p
$2 = 0x1d5dd31 ""
(gdb) p p1
$3 = 0x1d5dd30 " "
OK to check-in? Probably [obv].
Thanks,
Jan
2010-01-01 Jan Kratochvil <jan.kratochvil@redhat.com>
* cli/cli-script.c (process_next_line): Check P2 overrun.
--- a/gdb/cli/cli-script.c
+++ b/gdb/cli/cli-script.c
@@ -893,7 +893,7 @@ process_next_line (char *p, struct command_line **command, int parse_commands)
p2 = p;
/* Strip leading whitespace. */
- while (*p2 == ' ' || *p2 == '\t')
+ while (p2 != p1 && (*p2 == ' ' || *p2 == '\t'))
p2++;
/* 'end' is always recognized, regardless of parse_commands value.
next parent reply other threads:[~2010-01-01 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19258.59036.731093.439412@totara.tehura.co.nz>
[not found] ` <20091230054617.GA548@adacore.com>
[not found] ` <19259.54163.166299.854635@totara.tehura.co.nz>
2010-01-01 8:41 ` Jan Kratochvil [this message]
2010-01-01 10:36 ` Joel Brobecker
2010-01-01 11:01 ` Jan Kratochvil
2010-01-01 11:12 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100101084028.GA29969@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox