From: nickrob@snap.net.nz (Nick Roberts)
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: [Bug:cli] Loading user-defined function generates an internal error
Date: Wed, 30 Dec 2009 08:50:00 -0000 [thread overview]
Message-ID: <19259.5113.884675.579179@totara.tehura.co.nz> (raw)
In-Reply-To: <20091230054617.GA548@adacore.com>
> > If the user-defined function below is put in a file user.cmd, say, then in
> > internal error is generated upon loading it:
>
> I can reproduce too. Have you tried debugging the problem?
It's due to this change:
2009-11-18 Vladimir Prus <vladimir@codesourcery.com>
* cli/cli-script.c (process_next_line): Recognize 'end'
even when the line has leading space and we're not parsing
commands.
--
Nick http://users.snap.net.nz/~nickrob
next prev parent reply other threads:[~2009-12-30 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 5:35 Nick Roberts
2009-12-30 5:46 ` Joel Brobecker
2009-12-30 8:50 ` Nick Roberts [this message]
2009-12-31 6:27 ` Vladimir Prus
2009-12-30 22:26 ` Nick Roberts
2010-01-01 8:41 ` [patch] Fix crash on CLI indented comments [Re: [Bug:cli] Loading user-defined function generates an internal error] Jan Kratochvil
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=19259.5113.884675.579179@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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