<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- header_tag -->
<html lang="en">
<head>
<title>Error messages - GNU LilyPond program usage</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="GNU LilyPond program usage">
<meta name="generator" content="makeinfo 4.11">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Running-LilyPond.html#Running-LilyPond" title="Running LilyPond">
<link rel="prev" href="Command_002dline-usage.html#Command_002dline-usage" title="Command-line usage">
<link rel="next" href="Updating-files-with-convert_002dly.html#Updating-files-with-convert_002dly" title="Updating files with convert-ly">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1999--2007 by the authors
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.1 or any later version published by the Free Software
Foundation; with no Invariant Sections. A copy of the license is
included in the section entitled ``GNU Free Documentation
License''.
-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
hr { border:0; height:1; color: #000000; background-color: #000000; }
/* hr {
border: none;
height: 1px;
color: #666666;
background-color: #666666;
}
body {
border-left: 1px solid #666666;
border-right: 1px solid #666666;
color: #332d28;
margin-right: auto;
margin-left: auto;
width: 60em;
list-style-type: square;
font-family: Arial,Helvetica,sans-serif;
padding-right: 1em;
padding-left: 1em;
}
a {
border-bottom: 1px dashed #344242;
text-decoration: none;
color: #344242;
}
a:link {
text-decoration: none;
}
a:visited {
border-bottom: 1px dashed #666666;
color: #666666;
}
a:active {
border-bottom: 1px solid #00cccc;
color: #00cccc;
}
a:hover {
border-bottom: 1px solid #1d7b85;
color: #1d7b85;
}
blockquote {
border: 1px solid #cccccc;
padding: 3px;
width: 40em;
}
.node {
border-left: 1px solid #666666;
margin: -0.5em 0px 1em;
padding: 2px 1px 0px;
font-style: italic;
}
.node a {
border: none;
text-decoration: underline;
font-style: normal;
font-weight: bold;
}
.verbatim {
font-family: "Courier New",Courier,monospace;
}
.unnumberedsubsubsec {
font-size: large;
color: #1d7b85;
}
.subsubheading {
font-size: large;
color: #3b220d;
}
.contents {
border: 1px dashed #339999;
margin: 3px 2em;
list-style-type: square;
padding-right: 1em;
width: 40em;
background-color: #fcfff9;
}
.contents a {
border-bottom: 1px dashed #423d34;
text-decoration: none;
color: #423d34;
}
.contents a:visited {
border-bottom: 1px dashed #666666;
color: #666666;
}
.contents a:active {
border-bottom: 1px solid #f0d86d;
color: #f0d86d;
}
.contents a:hover {
border-bottom: 1px solid #3b220d;
color: #3b220d;
}
.menu {
border-left: 1px dashed #339999;
margin: 3px 2em 1em;
list-style-type: square;
padding-left: 1.4em;
width: 40em;
}
.unnumbered {
}
h2 {
font-size: x-large;
color: #1d7b85;
}
*/
--></style>
</head>
<BODY BGCOLOR=WHITE TEXT=BLACK>
<div class="node">
<p>
<a name="Error-messages"></a>
Next: <a rel="next" accesskey="n" href="Updating-files-with-convert_002dly.html#Updating-files-with-convert_002dly">Updating files with convert-ly</a>,
Previous: <a rel="previous" accesskey="p" href="Command_002dline-usage.html#Command_002dline-usage">Command-line usage</a>,
Up: <a rel="up" accesskey="u" href="Running-LilyPond.html#Running-LilyPond">Running LilyPond</a>
<hr>
</div>
<h3 class="section">3.3 Error messages</h3>
<p><a name="index-error-messages-26"></a>Different error messages can appear while compiling a file:
<dl>
<dt><em>Warning</em><dd><a name="index-warning-27"></a>Something looks suspect. If you are requesting something out of the
ordinary then you will understand the message, and can ignore it.
However, warnings usually indicate that something is wrong with the
input file.
<br><dt><em>Error</em><dd>Something is definitely wrong. The current processing step (parsing,
interpreting, or formatting) will be finished, but the next step will
be skipped.
<br><dt><em>Fatal error</em><dd><a name="index-error-28"></a><a name="index-fatal-error-29"></a>Something is definitely wrong, and LilyPond cannot continue. This
happens rarely. The most usual cause is misinstalled fonts.
<br><dt><em>Scheme error</em><dd><a name="index-trace_002c-Scheme-30"></a><a name="index-call-trace-31"></a><a name="index-Scheme-error-32"></a>Errors that occur while executing Scheme code are caught by the Scheme
interpreter. If running with the verbose option (<code>-V</code> or
<code>--verbose</code>) then a call trace of the offending
function call is printed.
<br><dt><em>Programming error</em><dd><a name="index-Programming-error-33"></a>There was some internal inconsistency. These error messages are
intended to help the programmers and debuggers. Usually, they can be
ignored. Sometimes, they come in such big quantities that they obscure
other output.
<br><dt><em>Aborted (core dumped)</em><dd>This signals a serious programming error that caused the program to
crash. Such errors are considered critical. If you stumble on one,
send a bug-report.
</dl>
<p><a name="index-errors_002c-message-format-34"></a>If warnings and errors can
be linked to some part of the input file, then error messages have the
following form
<pre class="example"> <var>filename</var>:<var>lineno</var>:<var>columnno</var>: <var>message</var>
<var>offending input line</var>
</pre>
<p>A line-break is inserted in the offending line to indicate the column
where the error was found. For example,
<pre class="example"> test.ly:2:19: error: not a duration: 5
{ c'4 e'
5 g' }
</pre>
<p>These locations are LilyPond's best guess about where the warning or
error occurred, but (by their very nature) warnings and errors occur
when something unexpected happens. If you can't see an error in the
indicated line of your input file, try checking one or two lines
above the indicated position.
<!-- footer_tag --><br><hr>
<div class="node">
<p>
Next: <a rel="next" accesskey="n" href="Updating-files-with-convert_002dly.html#Updating-files-with-convert_002dly">Updating files with convert-ly</a>,
Previous: <a rel="previous" accesskey="p" href="Command_002dline-usage.html#Command_002dline-usage">Command-line usage</a>,
Up: <a rel="up" accesskey="u" href="Running-LilyPond.html#Running-LilyPond">Running LilyPond</a>
</div>
<div style="background-color: #e8ffe8; padding: 2; border: #c0ffc0 1px solid;">
<p>
<font size="-1">
This page is for LilyPond-2.11.57 (development-branch).
<br>
<address>
Report errors to <a href="http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs">http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs</a>. </address>
<br>
Your <a href="http://lilypond.org/web/devel/participating/documentation-adding">suggestions for the documentation</a> are welcome.
</font>
</p>
</div>
<P>
Other languages: <a href="Error-messages.de.html">deutsch</a>.
<BR>
</P>
</BODY></html>
