Am Mittwoch, 2. Februar 2011, um 05:31:23 schrieb Jay Anderson:
On Tue, Feb 1, 2011 at 1:46 PM, Keith OHara k-ohara5...@oco.net wrote:
... on both WinXP and Linux and could not find a segfault.
It happens consistently for me (linux 2.6.35, x86_64).
Ah, I'm on 32-bit linux...
Since it's
On Mon, 31 Jan 2011 15:18:50 -0800, Neil Puttock n.putt...@gmail.com wrote:
On 31 January 2011 15:37, Reinhold Kainhofer reinh...@kainhofer.com wrote:
I can only reproduce it using a GUB binary.
I tried 2.13.40 and 2.13.47 binaries, from
download.linuxaudio.org/lilypond/binaries, on both
On Tue, Feb 1, 2011 at 1:46 PM, Keith OHara k-ohara5...@oco.net wrote:
... on both WinXP and Linux and could not find a segfault.
It happens consistently for me (linux 2.6.35, x86_64). Since it's such
a difficult to reproduce, narrow case it's probably best not to worry
about. Filling in the
Am Montag, 31. Januar 2011, um 05:01:14 schrieb Jay Anderson:
It actually occurred somewhere between 2.13.45 and 2.13.46 from what I can
tell.
Hmm, that's strange, as there was no commit touching the part-combiner between
2.13.45 and 2.13.46...
More info: I have two parts in the score like
On 31 January 2011 15:37, Reinhold Kainhofer reinh...@kainhofer.com wrote:
Unfortunately, I can't reproduce the problem with current master... I tried
running valgrind, but I only get some uninitialized variable warnings for the
usual *mark* functions (I sent a mail to lilypond-devel about
Am Dienstag, 1. Februar 2011, um 00:18:50 schrieb Neil Puttock:
On 31 January 2011 15:37, Reinhold Kainhofer reinh...@kainhofer.com wrote:
Unfortunately, I can't reproduce the problem with current master... I
tried running valgrind, but I only get some uninitialized variable
warnings for
On Sat, Jan 29, 2011 at 11:02 PM, Paul Scott waterho...@ultrasw.com wrote:
This says 2.13.48.
Right. In order to get debug symbols I built it out of git which is
2.13.48, but I originally saw the error with 2.13.47.
-Jay (fellow arizonian)
___
Jay Anderson horndude77 at gmail.com writes:
I haven't
been able to create a small example yet. I'm not sure I'll be able to
make one as any change makes the segfault go away. Anyway I hope this
stack trace is useful.
I wish you luck in making a small example.
Maybe you can test an earlier
On Sun, Jan 30, 2011 at 11:27 AM, Keith OHara k-ohara5...@oco.net wrote:
I wish you luck in making a small example.
Maybe you can test an earlier Lilypond version on your complete score?
Do you use Reinhold's new (not yet documented) \partcombineTogether, etc.,
that appeared in 2.13.35 ?
Below is the gdb trace from the segfault:
GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent
This says 2.13.48.
Paul Scott
On 01/29/2011 09:45 PM, Jay Anderson wrote:
Below is the gdb trace from the segfault:
GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or laterhttp://gnu.org/licenses/gpl.html
This is free software:
11 matches
Mail list logo
