Good.
Could you give some other scores a try with the patched release?
Michael
Am 07.06.2024 um 15:55 schrieb K. Blum:
Hi Michael,
yes, the initial MWE that I've posted now works fine with your patched
release.
Thank you for working on this!
Cheers,
Klaus
Am 06.06.2024 um 22:39 schrieb Mich
Hi Michael,
yes, the initial MWE that I've posted now works fine with your patched
release.
Thank you for working on this!
Cheers,
Klaus
Am 06.06.2024 um 22:39 schrieb Michael Käppler:
Hi Klaus,
I think I could track this down, see
https://gitlab.com/lilypond/lilypond/-/issues/6710 for an upd
Hi Klaus,
I think I could track this down, see
https://gitlab.com/lilypond/lilypond/-/issues/6710 for an update.
It would be great if you could test the following patched release with the
file that failed initially. I uploaded the zip archive on WeTransfer:
https://we.tl/t-kW6yGIdJau
Unfortunate
Hi Klaus,
thanks for reporting, I can confirm this behaviour on my Windows machine.
Now tracked as https://gitlab.com/lilypond/lilypond/-/issues/6710
Michael
Am 21.04.2024 um 18:39 schrieb K. Blum:
Hi Michael,
Am 12.04.2024 um 18:00 schrieb bug-lilypond-requ...@gnu.org:
This seems to be:
htt
Hi Michael,
Am 12.04.2024 um 18:00 schrieb bug-lilypond-requ...@gnu.org:
This seems to be:
https://gitlab.com/lilypond/lilypond/-/issues/6687
Should be fixed in the upcoming release 2.25.15.
Thanks for that information.
Unfortunately the problem still persists in the 2.25.15 Windows build.
D
Am 11.04.2024 um 22:05 schrieb Aaron Hill via bug-lilypond:
Seems to be something specific to the Windows build. I could not
reproduce the failing assertion on the Linux builds of LilyPond also
running Guile 3.0.9. I could reproduce it with the 2.25.14 Windows
build using scheme-sandbox.ly
On 2024-04-11 10:12 am, K. Blum via bug-lilypond wrote:
Starte lilypond.exe 2.25.14 [mwe scheme.ly]...
»C:/Users/Flower/Desktop/mwe scheme.ly« wird verarbeitet
Analysieren.../home/lily/lilypond-2.25.14/release/binaries/mingw/dependencies/src/guile-3.0.9/libguile/integers.c:115:
assertion failed
« wird verarbeitet
Analysieren.../home/lily/lilypond-2.25.14/release/binaries/mingw/dependencies/src/guile-3.0.9/libguile/integers.c:115:
assertion failed
Wurde mit dem Return-Code 3 beendet.
In the past, I never had this problem (2.20, 2.18, ...).
Also tested now with 2.24.3, 2.25.1, 2.25.6, 2.25.9
anders.vin...@bek.no writes:
> a> a4cc910a Issue 2787: Sanitize usage of -DDEBUG, -DNDEBUG and assert
>
> With the change from -NDEBUG to -DEBUG in commit , quite a few
> scores makes lilypond crash. The same happens with releases since then
> (19.21++). The behavior is the same whether DEBU
> On Tue, 27 Oct 2015 12:18:27 +1100, Andrew Bernard
> said:
A> Using 2.19.30, hoping to avoid the core dumps from 2.19.29, I get
A> the following error on my moderately large score: Preprocessing
A> graphical objects...lilypond:
A>
/home/gub/NewGub/gub/target/linux-64/s
Debugger backtrace attached.
This is from 2.19.30.
Andrew
backtrace
Description: Binary data
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Andrew Bernard writes:
> Using 2.19.30, hoping to avoid the core dumps from 2.19.29, I get the
> following error on my moderately large score:
>
> Preprocessing graphical objects...lilypond:
> /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/i
Using 2.19.30, hoping to avoid the core dumps from 2.19.29, I get the following
error on my moderately large score:
Preprocessing graphical objects...lilypond:
/home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/interval.hh:227:
T Inter
Thomas Morley gmail.com> writes:
> Example #1 gives a warning in 2.18.2, aborting in 2.19.21
>
> > EXAMPLE #1 (see http://lists.gnu.org/archive/html/lilypond-user/2015-06/
msg00278.html)
I added https://code.google.com/p/lilypond/issues/detail?id=4447
> Example #2 gives no error or warning her
2015-06-13 21:44 GMT+02:00 Simon Albrecht :
> Am 13.06.2015 um 20:03 schrieb Thomas Morley:
>>
>> 2015-06-13 19:16 GMT+02:00 Daniel Rosen :
>>>
>>> Running LilyPond 2.19.21 on 64-bit Windows 7, I get an odd pop-up error
>>> dialog in a number of different circumstances. Below are two examples.
>>
>
> -Original Message-
> From: Simon Albrecht [mailto:simon.albre...@mail.de]
> Sent: Saturday, June 13, 2015 3:45 PM
> To: Thomas Morley; Daniel Rosen
> Cc: bug-lilypond@gnu.org
> Subject: Re: "Assertion failed!" errors
>
> Am 13.06.2015 um 20:03 schrieb
Am 13.06.2015 um 20:03 schrieb Thomas Morley:
2015-06-13 19:16 GMT+02:00 Daniel Rosen :
Running LilyPond 2.19.21 on 64-bit Windows 7, I get an odd pop-up error dialog
in a number of different circumstances. Below are two examples.
Example #1 gives a warning in 2.18.2, aborting in 2.19.21
Thou
> -Original Message-
> From: Daniel Rosen
> Sent: Saturday, June 13, 2015 2:22 PM
> To: 'Thomas Morley'
> Cc: bug-lilypond@gnu.org
> Subject: RE: "Assertion failed!" errors
>
> Changing #'Stem to #'NoteHead allows the code to compile e
> -Original Message-
> From: Thomas Morley [mailto:thomasmorle...@gmail.com]
> Sent: Saturday, June 13, 2015 2:04 PM
> To: Daniel Rosen
> Cc: bug-lilypond@gnu.org
> Subject: Re: "Assertion failed!" errors
>
> Example #1 gives a warning in 2.18.2, aborting
2015-06-13 20:33 GMT+02:00 Daniel Rosen :
>> -Original Message-
>> From: Daniel Rosen
>> Sent: Saturday, June 13, 2015 2:30 PM
>> To: 'Thomas Morley'
>> Cc: 'bug-lilypond@gnu.org'
>> Subject: RE: "Assertion failed!" errors
> -Original Message-
> From: Daniel Rosen
> Sent: Saturday, June 13, 2015 2:30 PM
> To: 'Thomas Morley'
> Cc: 'bug-lilypond@gnu.org'
> Subject: RE: "Assertion failed!" errors
>
> I did some more tweaking, and came up with the followin
2015-06-13 20:22 GMT+02:00 Daniel Rosen :
>> -Original Message-
>> From: Thomas Morley [mailto:thomasmorle...@gmail.com]
>> Sent: Saturday, June 13, 2015 2:04 PM
>> To: Daniel Rosen
>> Cc: bug-lilypond@gnu.org
>> Subject: Re: "Assertion failed!&qu
2015-06-13 19:16 GMT+02:00 Daniel Rosen :
> Running LilyPond 2.19.21 on 64-bit Windows 7, I get an odd pop-up error
> dialog in a number of different circumstances. Below are two examples.
Example #1 gives a warning in 2.18.2, aborting in 2.19.21
Though it's not a bug but expected behaviour, bec
Running LilyPond 2.19.21 on 64-bit Windows 7, I get an odd pop-up error dialog
in a number of different circumstances. Below are two examples.
EXAMPLE #1 (see
http://lists.gnu.org/archive/html/lilypond-user/2015-06/msg00278.html)
Given the following code,
\version "2.19.21"
\new Voice \with {
On Thu, Nov 22, 2012 at 11:46:07AM +, Ian Hulin wrote:
> Hi Colin, Keith and Walter,
> On 22/11/12 09:19, Colin Hall wrote:
> > On Wed, Nov 21, 2012 at 05:08:52AM +, Keith OHara wrote:
> >> The released builds are not compiled this way, so no-one can
> >> reproduce your bug without using Li
Hi Colin, Keith and Walter,
On 22/11/12 09:19, Colin Hall wrote:
> On Wed, Nov 21, 2012 at 05:08:52AM +, Keith OHara wrote:
>> Werner LEMBERG gnu.org> writes:
>>
>>> This time I tried with current git (commit 436824b8):
>>>
../flower/include/interval.hh:226: T Interval_t::center()
On Wed, Nov 21, 2012 at 05:08:52AM +, Keith OHara wrote:
> Werner LEMBERG gnu.org> writes:
>
> > This time I tried with current git (commit 436824b8):
> >
> > > ../flower/include/interval.hh:226:
> > > T Interval_t::center() const [with T = double]:
> > > Assertion `!is_empty ()' f
>> - y = me->get_bound (dir)->extent (common_y, Y_AXIS).center ();
>> + Interval ii = me->get_bound (dir)->extent (common_y, Y_AXIS);
>> + if (!ii.is_empty())
>> +y = ii.center ();
>
> This works, thanks, and I get output which looks like being
> predictable (see attached image), assuming
>> Misleading?
>
> That backtrace described a call to center() that would have
> succeeded, if it were allowed to continue.
Ah, yes, silly me.
> Let the assert fail, then backtrace after the program exits, or set
> a conditional breakpoint depending on the (negative of the)
> condition in the as
On Tue, 20 Nov 2012 22:55:21 -0800, Werner LEMBERG wrote:
BTW, here is a full backtrace (of the first 32 frames).
#0 Interval_t::center (this=0xbfff96ec)
at ../flower/include/interval.hh:226
#1 0x082d9cdd in Note_head::get_stem_attachment (fm=0x8602ec8, key=...)
at note-head.cc:181
>> I'm on a GNU/Linux box, running `autogen.sh' with
>> `--disable-optimising', and compiling with g++ 4.6.2.
>
> The released builds are not compiled this way, so no-one can
> reproduce your bug without using Linux to create a debug-enabled
> build.
Well, assertion aborts should *never* happen, s
Werner LEMBERG gnu.org> writes:
> This time I tried with current git (commit 436824b8):
>
> > ../flower/include/interval.hh:226:
> > T Interval_t::center() const [with T = double]:
> > Assertion `!is_empty ()' failed.
> I'm on a GNU/Linux box, running `autogen.sh' with
> `--disable-op
> ../flower/include/interval.hh:226:
> T Interval_t::center() const [with T = double]:
> Assertion `!is_empty ()' failed.
BTW, here is a full backtrace (of the first 32 frames).
Werner
==
#0 Interval_t::center (
This time I tried with current git (commit 436824b8):
>> \version "2.17.6"
>>
>> {
>> f2 \glissando
>> \override NoteHead #'stencil = ##f
>> e |
>> }
>>
>> causes the following output (beautified):
>
> no such messages wit 2.17.7 - but there is no glissando; use
> transpar
Eluze wrote
> use transparent instead.
or #'stencil = #point-stencil
which lets the ledger lines diappear
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/2-17-6-assertion-failed-with-glissando-tp136531p136613.html
Sent from the Bugs mailing list ar
h messages wit 2.17.7 - but there is no glissando; use transparent
instead.
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/2-17-6-assertion-failed-with-glissando-tp136531p136612.html
Sent from the Bugs mailing list archive at Nabble.com.
[commit 3bd44774]
The following code
\version "2.17.6"
{
f2 \glissando
\override NoteHead #'stencil = ##f
e |
}
causes the following output (beautified):
GNU LilyPond 2.17.6
Processing `bug.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
On Friday 22 October 2004 00.49, Takács Gábor wrote:
> Hi!
>
> While creating a multi-voice sheet with LilyPond 2.2.6
> I encoutered an "assertion failed" error.
>
> I attached a simplified version of my .ly file
> that produces the error.
Thanks for your repor
Hi!
While creating a multi-voice sheet with LilyPond 2.2.6
I encoutered an "assertion failed" error.
I attached a simplified version of my .ly file
that produces the error.
$ lilypond assertion_failed.ly
> lilypond (GNU LilyPond) 2.2.6
> Running lilypond-bin...
[EMAIL PROTECTED] writes:
> Here is a minimized .ly file that should reproduce the bug. It looks like
> it's triggered by the slur ending with a rest instead of a note. I think
> that came about because I had converted an old and hairy file from version
> 1.6.6 or even earlier. I can't recall wh
Here is a minimized .ly file that should reproduce the bug. It looks like
it's triggered by the slur ending with a rest instead of a note. I think
that came about because I had converted an old and hairy file from version
1.6.6 or even earlier. I can't recall whether the original sheet music
act
[EMAIL PROTECTED] writes:
> I ran into an assertion failure in lilypond 2.0.0. My understanding is
> that assertions are never supposed to fail, so I take it this could be a
> serious bug.
>
> This is the error message I get:
>
> > lilypond-bin: bezier.cc:77: Real Bezier::get_other_coordinate(Ax
I ran into an assertion failure in lilypond 2.0.0. My understanding is
that assertions are never supposed to fail, so I take it this could be a
serious bug.
This is the error message I get:
> lilypond-bin: bezier.cc:77: Real Bezier::get_other_coordinate(Axis, double)
> const: Assertion `fabs (c[
43 matches
Mail list logo
