From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: grub-devel@gnu.org
Subject: script bug
Date: Sun, 7 May 2006 07:42:15 +0200 [thread overview]
Message-ID: <200605070742.15975.okuji@enbug.org> (raw)
Try something like this:
@ "extremely long long
line............................................................." {
}
grub-emu segfaults. This is partially because of the menu code, partilaly
because of the scripting engine code. The menu code currently limits the max
number of characters per line to 100 (very bad). So get_line chops the line,
then the scripting engine cannot deal with the malformed line. Both must be
fixed.
Okuji
next reply other threads:[~2006-05-07 5:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 5:42 Yoshinori K. Okuji [this message]
2006-05-07 11:40 ` script bug Marco Gerards
2006-05-07 14:58 ` Yoshinori K. Okuji
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=200605070742.15975.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.