Re: French beams over rests cause segfault

[Phil Holmes]

"Jean Menezes da Rocha"  wrote in message 
news:CALRb6h+_gWgeU1=6wruogawua7hsddya8zx0vsy97is7tci...@mail.gmail.com...
I have seen, according to this  
[1],

that Kastrup created a patch to address this issue. Is there any way I can
apply this patch by now, or should I wait for a new development release
containing a definitive solution?
If this is not the right place/time to ask this question, feel free to
dismiss my request (but pointing me to the
right place to ask will be appreciated).


In order to apply the patch to your own system, you will need to be able to 
compile LilyPond yourself: see 
http://lilypond.org/doc/v2.19/Documentation/contributor/overview-of-compiling


This is likely to be fairly onerous.  You may find it better to wait for a 
pre-compiled version - all other things being equal this should be available 
next Monday (the 9th).


--
Phil Holmes



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: French beams over rests cause segfault

[Simon Albrecht]

On 05.11.2015 14:45, Jean Menezes da Rocha wrote:
I have seen, according to this 
 [1], that Kastrup created 
a patch to address this issue. Is there any way I can
apply this patch by now, or should I wait for a new development 
release containing a definitive solution?
If this is not the right place/time to ask this question, feel free to 
dismiss my request (but pointing me to the

right place to ask will be appreciated).


It’s not going to be overly long until the next development release, 
normally 2 to 4 weeks at most. But yes, you can apply the patch locally, 
by pulling the source code, applying the patch and compiling LilyPond 
yourself. Instructions may be found at 
.


HTH, Simon

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: French beams over rests cause segfault

[Jean Menezes da Rocha]

Thanks Simon,
I am gonna take a risk and try to compile a patched version using the .diff
file.

Best regards!

On Thu, Nov 5, 2015 at 11:52 AM, Simon Albrecht 
wrote:

> On 05.11.2015 14:45, Jean Menezes da Rocha wrote:
>
>> I have seen, according to this 
>> [1], that Kastrup created a patch to address this issue. Is there any way I
>> can
>> apply this patch by now, or should I wait for a new development release
>> containing a definitive solution?
>> If this is not the right place/time to ask this question, feel free to
>> dismiss my request (but pointing me to the
>> right place to ask will be appreciated).
>>
>
> It’s not going to be overly long until the next development release,
> normally 2 to 4 weeks at most. But yes, you can apply the patch locally, by
> pulling the source code, applying the patch and compiling LilyPond
> yourself. Instructions may be found at <
> http://lilypond.org/doc/v2.19/Documentation/contributor/compiling>.
>
> HTH, Simon
>



-- 
Jean Menezes da Rocha
Compositor
Professor -- Faculdades Est
Mestre e Doutorando em Composição pela Universidade Federal da Bahia
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: French beams over rests cause segfault

[Jean Menezes da Rocha]

I have seen, according to this  [1],
that Kastrup created a patch to address this issue. Is there any way I can
apply this patch by now, or should I wait for a new development release
containing a definitive solution?
If this is not the right place/time to ask this question, feel free to
dismiss my request (but pointing me to the
right place to ask will be appreciated).

Thanks for your attention and for your outstanding work!

On Tue, Nov 3, 2015 at 9:28 AM, Simon Albrecht 
wrote:

> Hello Jean,
>
> thanks for the additional info. Please always reply on-list, that way
> others can pick up the process etc.
>
> Yours, Simon
>
> On 03.11.2015 02:01, Jean Menezes da Rocha wrote:
>
>> Now I see I haven't added some important details:
>>
>> I am running Lilypond 2.19.30 from Antergos Linux 64-bit. I am using the
>> lilypond-devel package provided by the AUR.
>> I did not try to reproduce this bug in any other environment.
>>
>> Let me know if I can provide any further help!
>>
>> On Mon, Nov 2, 2015 at 9:34 PM, Jean Menezes da Rocha <
>> j...@menezesdarocha.info > wrote:
>>
>> Sure. Here you are:
>>
>> GNU gdb (GDB) 7.10
>> Copyright (C) 2015 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later
>> 
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.  Type "show
>> copying"
>> and "show warranty" for details.
>> This GDB was configured as "x86_64-unknown-linux-gnu".
>> Type "show configuration" for configuration details.
>> For bug reporting instructions, please see:
>> .
>> Find the GDB manual and other documentation resources online at:
>> .
>> For help, type "help".
>> Type "apropos word" to search for commands related to "word"...
>> Reading symbols from lilypond...(no debugging symbols found)...done.
>> (gdb) r example.ly 
>> Starting program: /usr/bin/lilypond example.ly 
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/usr/lib/libthread_db.so.1".
>> GNU LilyPond 2.19.30
>> Processing `example.ly '
>>
>> Parsing...
>> Interpreting music...
>> Preprocessing graphical objects...
>> Finding the ideal number of pages...
>> Fitting music on 1 page...
>> Drawing systems...
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x7793df7e in scm_c_memq () from /usr/lib/libguile.so.17
>> (gdb) bt full
>> #0  0x7793df7e in scm_c_memq () from /usr/lib/libguile.so.17
>> No symbol table info available.
>> #1  0x005aa9c9 in ?? ()
>> No symbol table info available.
>> #2  0x006b74db in ?? ()
>> No symbol table info available.
>> #3  0x006b8f3b in ?? ()
>> No symbol table info available.
>> #4  0x005aa631 in ?? ()
>> No symbol table info available.
>> #5  0x779216f3 in ?? () from /usr/lib/libguile.so.17
>> No symbol table info available.
>> #6  0x77920bbc in scm_dapply () from /usr/lib/libguile.so.17
>> No symbol table info available.
>> #7  0x00650f93 in ?? ()
>> No symbol table info available.
>> #8  0x005aab7f in ?? ()
>> No symbol table info available.
>> #9  0x779204d2 in scm_dapply () from /usr/lib/libguile.so.17
>> No symbol table info available.
>> #10 0x00650f93 in ?? ()
>> No symbol table info available.
>> #11 0x005ac46c in ?? ()
>> No symbol table info available.
>> #12 0x779204d2 in scm_dapply () from /usr/lib/libguile.so.17
>> No symbol table info available.
>> #13 0x00650f93 in ?? ()
>> No symbol table info available.
>> #14 0x004e02a7 in ?? ()
>> No symbol table info available.
>> #15 0x779204d2 in scm_dapply () from /usr/lib/libguile.so.17
>> No symbol table info available.
>> #16 0x00650f93 in ?? ()
>> No symbol table info available.
>> #17 0x006a03c0 in ?? ()
>> No symbol table info available.
>> #18 0x006a0fdb in ?? ()
>> No symbol table info available.
>> ---Type  to continue, or q  to quit---
>> #19 0x006a2bd1 in ?? ()
>> No symbol table info available.
>> #20 0x779204d2 in scm_dapply () from /usr/lib/libguile.so.17
>> No symbol table info available.
>> #21 0x00650f93 in ?? ()
>> No symbol table info available.
>> #22 0x006db753 in ?? ()
>> No symbol table info available.
>> #23 0x006dc977 in ?? ()
>> No symbol table info available.
>> #24 0x005777dc in ?? ()