Hello,
On Thu, Aug 08, 2013 at 01:47:29PM +0200, Petr Gajdos wrote:
Reply to 'Make doc crashing on my PC' thread started on 22 Jun 2013.
Hi list,
I have same symptomps like Phil described.
Snippet of build log:
-8--
Petr Gajdos pgaj...@suse.cz writes:
On Thu, Aug 08, 2013 at 01:47:29PM +0200, Petr Gajdos wrote:
Reply to 'Make doc crashing on my PC' thread started on 22 Jun 2013.
Hi list,
I have same symptomps like Phil described.
Snippet of build log:
Phil Holmes mail at philholmes.net writes:
From: David Kastrup dak at gnu.org
Keith OHara k-ohara5a5a at oco.net writes:
Petr Gajdos pgajdos at suse.cz writes:
I have same symptoms like Phil described.
Core was generated by `/usr/bin/lilypond -dpreview -dresolution=150 -o
./
Hello,
On 10 August 2013 01:07, Keith OHara k-ohara5...@oco.net wrote:
Phil Holmes mail at philholmes.net writes:
- Original Message -
that reason at least on my machine. It seems to me therefore that
2.17.18
do not expose the issue but 2.17.19 does.
That stacks up well
On Fri, 09 Aug 2013 23:58:25 -0700, James pkx1...@gmail.com wrote:
[...]
Then I got this:
jlowe@jlowe26vm ~/Desktop$ lilypond -dpreview -dresolution=150 -o hello
orchestra.ly
GNU LilyPond 2.17.19
programming error: Parsed object should be dead: #Context_mod ((push
VerticalAxisGroup #t
James pkx1...@gmail.com writes:
So whatever is going on is obviously not consistent :)
cat /proc/sys/kernel/randomize_va_space
If you get something different from 0, try
echo 0|sudo tee /proc/sys/kernel/randomize_va_space
and then do repeated experiments. I think that it's quite likely
Hello,
On 10 August 2013 08:23, Keith OHara k-ohara5...@oco.net wrote:
On Fri, 09 Aug 2013 23:58:25 -0700, James pkx1...@gmail.com wrote:
[...]
Then I got this:
jlowe@jlowe26vm ~/Desktop$ lilypond -dpreview -dresolution=150 -o hello
orchestra.ly
GNU LilyPond 2.17.19
programming
Hello
On 10 August 2013 08:28, David Kastrup d...@gnu.org wrote:
James pkx1...@gmail.com writes:
So whatever is going on is obviously not consistent :)
cat /proc/sys/kernel/randomize_va_space
got '2'
If you get something different from 0, try
echo 0|sudo tee
In case this escaped people's notice: there is now an issue for this
URL:http://code.google.com/p/lilypond/issues/detail?id=3490 and I have
posted a patch based on the memory issue and stencil-stack
buzzwords. I think I'll just push it to staging: it's not like it could
make anything worse.
James pkx1...@gmail.com writes:
Hello
On 10 August 2013 08:28, David Kastrup d...@gnu.org wrote:
James pkx1...@gmail.com writes:
So whatever is going on is obviously not consistent :)
cat /proc/sys/kernel/randomize_va_space
got '2'
If you get something different from 0, try
cat /proc/sys/kernel/randomize_va_space
If you get something different from 0, try
echo 0|sudo tee /proc/sys/kernel/randomize_va_space
and then do repeated experiments. I think that it's quite likely things
will be more repeatable after that.
Maybe it also helps to set the following
Keith OHara k-ohara5...@oco.net writes:
Petr Gajdos pgajdos at suse.cz writes:
I have same symptoms like Phil described.
Core was generated by `/usr/bin/lilypond -dpreview -dresolution=150 -o ./
out-www orchestra.ly'.
If I understand correctly, this gives a way to reproduce the bug, on a
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Saturday, August 10, 2013 9:37 PM
Subject: Re: wrt 'Make doc crashing on my PC'
Keith OHara k-ohara5...@oco.net writes:
Petr Gajdos pgajdos at suse.cz writes:
I have same symptoms like Phil
If I haven't done mistake somewhere,
/home/abuild/rpmbuild/BUILD/lilypond-2.17.18/scripts/build/out/run-and-check
/usr/bin/lilypond -dpreview -dresolution=150 -o ./out-www
orchestra.ly orchestra.preview.log
succedes while
- Original Message -
From: Petr Gajdos pgaj...@suse.cz
To: lilypond-devel@gnu.org
Sent: Friday, August 09, 2013 11:07 AM
Subject: Re: wrt 'Make doc crashing on my PC'
that reason at least on my machine. It seems to me therefore that 2.17.18
do not expose the issue but 2.17.19 does
Phil Holmes m...@philholmes.net writes:
- Original Message -
From: Petr Gajdos pgaj...@suse.cz
To: lilypond-devel@gnu.org
Sent: Friday, August 09, 2013 11:07 AM
Subject: Re: wrt 'Make doc crashing on my PC'
that reason at least on my machine. It seems to me therefore that 2.17.18
Phil Holmes mail at philholmes.net writes:
- Original Message -
that reason at least on my machine. It seems to me therefore that
2.17.18
do not expose the issue but 2.17.19 does.
That stacks up well with my earlier investigations. Git besect
identified
Reply to 'Make doc crashing on my PC' thread started on 22 Jun 2013.
Hi list,
I have same symptomps like Phil described.
Snippet of build log:
-8--
/home/abuild/rpmbuild/BUILD/lilypond-2.17.23/scripts/build/out/run-and-check
/usr/bin/lilypond
- Original Message -
From: Petr Gajdos pgaj...@suse.cz
To: lilypond-devel@gnu.org
Sent: Thursday, August 08, 2013 12:47 PM
Subject: wrt 'Make doc crashing on my PC'
Reply to 'Make doc crashing on my PC' thread started on 22 Jun 2013.
Hi list,
I have same symptomps like Phil
On Thu, Aug 08, 2013 at 12:54:58PM +0100, Phil Holmes wrote:
Which OS are you using?
openSUSE factory.
Petr
signature.asc
Description: Digital signature
___
lilypond-devel mailing list
lilypond-devel@gnu.org
- Original Message -
From: Petr Gajdos pgaj...@suse.cz
To: lilypond-devel@gnu.org
Sent: Thursday, August 08, 2013 12:58 PM
Subject: Re: wrt 'Make doc crashing on my PC'
On Thu, Aug 08, 2013 at 12:54:58PM +0100, Phil Holmes wrote:
Which OS are you using?
openSUSE factory.
Petr
32
hello,
On 08/08/13 12:47, Petr Gajdos wrote:
Reply to 'Make doc crashing on my PC' thread started on 22 Jun 2013.
Hi list,
I have same symptomps like Phil described.
Snippet of build log:
-8--
On Thu, Aug 08, 2013 at 01:08:23PM +0100, Phil Holmes wrote:
- Original Message - From: Petr Gajdos pgaj...@suse.cz
To: lilypond-devel@gnu.org
Sent: Thursday, August 08, 2013 12:58 PM
Subject: Re: wrt 'Make doc crashing on my PC'
On Thu, Aug 08, 2013 at 12:54:58PM +0100, Phil Holmes
mean, however,
that I can't run patchy.
--
Phil Holmes
- Original Message -
From: James
To: lilypond-devel@gnu.org
Sent: Thursday, August 08, 2013 1:27 PM
Subject: Re: wrt 'Make doc crashing on my PC'
hello,
On 08/08/13 12:47, Petr Gajdos wrote:
Reply to 'Make doc
Petr Gajdos pgaj...@suse.cz writes:
On Thu, Aug 08, 2013 at 01:08:23PM +0100, Phil Holmes wrote:
- Original Message - From: Petr Gajdos pgaj...@suse.cz
To: lilypond-devel@gnu.org
Sent: Thursday, August 08, 2013 12:58 PM
Subject: Re: wrt 'Make doc crashing on my PC'
On Thu, Aug 08
On Thu, Aug 08, 2013 at 04:11:06PM +0200, David Kastrup wrote:
I don't have a 64bit system available. Can you send me a disassembly of
the axis_aligned_side_helper routine? I have the suspicion that the
code generated for it may be fishy.
Here you are, hth.
Thanks,
Petr
(gdb) disassemble
Petr Gajdos pgaj...@suse.cz writes:
On Thu, Aug 08, 2013 at 04:11:06PM +0200, David Kastrup wrote:
I don't have a 64bit system available. Can you send me a disassembly of
the axis_aligned_side_helper routine? I have the suspicion that the
code generated for it may be fishy.
Here you are,
On Thu, Aug 08, 2013 at 05:29:45PM +0200, David Kastrup wrote:
Thanks. Turns out I did not find what I was suspecting. So I need to
look further. That was the crashing executable, right?
I build with
LILYPOND_EXTERNAL_BINARY=/usr/bin/lilypond \
LILYPOND_BINARY=/usr/bin/lilypond \
make doc
James pkx1...@gmail.com writes:
hello,
On 08/08/13 12:47, Petr Gajdos wrote:
Reply to 'Make doc crashing on my PC' thread started on 22 Jun 2013.
Hi list,
I have same symptomps like Phil described.
Snippet of build log:
-8--
Petr Gajdos pgajdos at suse.cz writes:
I have same symptoms like Phil described.
Core was generated by `/usr/bin/lilypond -dpreview -dresolution=150 -o ./
out-www orchestra.ly'.
If I understand correctly, this gives a way to reproduce the bug,
on a 64-bit GNU/Linux system, without building
- Original Message -
From: Keith OHara k-ohara5...@oco.net
To: lilypond-devel@gnu.org
Sent: Thursday, August 08, 2013 9:27 PM
Subject: Re: wrt 'Make doc crashing on my PC'
One thing that doesn't fit my theory is Phil's report that changing almost
anything in the input file avoids
31 matches
Mail list logo
