Re: Strange error with no traceable cause.
Karlin High writes: > On 6/5/2018 4:02 PM, Thomas Morley wrote: >>> For running gdb do: >>> >>> gdb path/to/lilypond-executable >>> >>> For example: gdb lilypond-git/build/out/bin/lilypond >>> You will get some infos about gdb returned, finally it ends with >>> (gdb) >>> >>> Then type: >>> run path/to/the/ly-file >> I forgot, type: >> >> bt >> >> to get the stack and then: >> >>> Post the output. > > Watching and learning about gdb... Does this work for "standard" > LilyPond distributions? Or only for compiled-from-source with > debugging symbols or something? The backtrace usually at least is good for the function names even without debug information. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange error with no traceable cause.
On 6/5/2018 4:02 PM, Thomas Morley wrote: For running gdb do: gdb path/to/lilypond-executable For example: gdb lilypond-git/build/out/bin/lilypond You will get some infos about gdb returned, finally it ends with (gdb) Then type: run path/to/the/ly-file I forgot, type: bt to get the stack and then: Post the output. Watching and learning about gdb... Does this work for "standard" LilyPond distributions? Or only for compiled-from-source with debugging symbols or something? -- Karlin High Missouri, USA ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange error with no traceable cause.
2018-06-05 22:45 GMT+02:00 Thomas Morley : > 2018-06-05 22:35 GMT+02:00 : >> Mensagem Original >> Ativo 5 de jun de 2018 17:30, David Kastrup < d...@gnu.org> escreveu: >> >> crimsonsunr...@protonmail.com writes: >> >>> Well, I don't have any experience with gdb, so I wouldn't know what to >>> do. The strange thing seems to be that, if the score is engraved using >>> Frescobaldi's verbose output ( which has a separate engrave button ), >>> the error doesn't happen. >> >> That's not unusual for such garbage collection errors: triggering them >> requires a garbage collection occuring at an inopportune point of time >> and the time depends on how much memory is being temporarily used. With >> verbose output, more memory is churned through because of the storage >> the formatting of the verbose output requires, and thus garbage >> collection happens at different points of time than without verbose >> output. >> >> That makes these kind of error annoyingly hard to track down: they >> vanish and reappear with completely unrelated changes in usage and the >> actual error message is triggered at a time far from the problem. >> >> -- >> David Kastrup >> >> The most I can do is see if I can upload the files so other people can see >> if the same error happens on other machines. > > > For running gdb do: > > gdb path/to/lilypond-executable > > For example: gdb lilypond-git/build/out/bin/lilypond > You will get some infos about gdb returned, finally it ends with > (gdb) > > Then type: > run path/to/the/ly-file I forgot, type: bt to get the stack and then: > Post the output. > > > Cheers, > Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange error with no traceable cause.
2018-06-05 22:35 GMT+02:00 : > Mensagem Original > Ativo 5 de jun de 2018 17:30, David Kastrup < d...@gnu.org> escreveu: > > crimsonsunr...@protonmail.com writes: > >> Well, I don't have any experience with gdb, so I wouldn't know what to >> do. The strange thing seems to be that, if the score is engraved using >> Frescobaldi's verbose output ( which has a separate engrave button ), >> the error doesn't happen. > > That's not unusual for such garbage collection errors: triggering them > requires a garbage collection occuring at an inopportune point of time > and the time depends on how much memory is being temporarily used. With > verbose output, more memory is churned through because of the storage > the formatting of the verbose output requires, and thus garbage > collection happens at different points of time than without verbose > output. > > That makes these kind of error annoyingly hard to track down: they > vanish and reappear with completely unrelated changes in usage and the > actual error message is triggered at a time far from the problem. > > -- > David Kastrup > > The most I can do is see if I can upload the files so other people can see > if the same error happens on other machines. For running gdb do: gdb path/to/lilypond-executable For example: gdb lilypond-git/build/out/bin/lilypond You will get some infos about gdb returned, finally it ends with (gdb) Then type: run path/to/the/ly-file Post the output. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange error with no traceable cause.
Mensagem Original Ativo 5 de jun de 2018 17:30, David Kastrup escreveu: crimsonsunr...@protonmail.com writes: > Well, I don't have any experience with gdb, so I wouldn't know what to > do. The strange thing seems to be that, if the score is engraved using > Frescobaldi's verbose output ( which has a separate engrave button ), > the error doesn't happen. That's not unusual for such garbage collection errors: triggering them requires a garbage collection occuring at an inopportune point of time and the time depends on how much memory is being temporarily used. With verbose output, more memory is churned through because of the storage the formatting of the verbose output requires, and thus garbage collection happens at different points of time than without verbose output. That makes these kind of error annoyingly hard to track down: they vanish and reappear with completely unrelated changes in usage and the actual error message is triggered at a time far from the problem. -- David Kastrup The most I can do is see if I can upload the files so other people can see if the same error happens on other machines.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange error with no traceable cause.
crimsonsunr...@protonmail.com writes: > Well, I don't have any experience with gdb, so I wouldn't know what to > do. The strange thing seems to be that, if the score is engraved using > Frescobaldi's verbose output ( which has a separate engrave button ), > the error doesn't happen. That's not unusual for such garbage collection errors: triggering them requires a garbage collection occuring at an inopportune point of time and the time depends on how much memory is being temporarily used. With verbose output, more memory is churned through because of the storage the formatting of the verbose output requires, and thus garbage collection happens at different points of time than without verbose output. That makes these kind of error annoyingly hard to track down: they vanish and reappear with completely unrelated changes in usage and the actual error message is triggered at a time far from the problem. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange error with no traceable cause.
Mensagem Original Ativo 5 de jun de 2018 16:43, David Kastrup escreveu: crimsonsunr...@protonmail.com writes: > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ > > On 5 June 2018 2:33 PM, David Kastrup wrote: > >> crimsonsunr...@protonmail.com writes: >> >> > I'm working on a large score using 2.21.0, parts all separated into >> > >> > different files and such, suddenly, after adding a bar for the 3rd >> > >> > clarinet, this shows up: >> > >> > Parsing... >> > >> > Interpreting music...[8][16]ERROR: In procedure ly:trampoline: >> > >> > ERROR: Wrong type argument in position 3 (expecting Translator): >> > >> > # >> > >> > I have no idea why this is happening. All the other parts add fine >> > >> > but, as soon as the bar is added for that particular instrument, the >> > >> > error shows up. >> > >> > However, if you engrave with verbose output on Frescobaldi >> > >> > enabled...the error doesn't show up. Disable that and do normal >> > >> > engraving...Same error. >> > >> > Any ideas on what's causing it or it might be a Fescobaldi bug? >> >> This is an error in the internals of the memory organization of >> >> LilyPond. Which platform are you using this on, and which version of >> >> Guile has been compiled into it? >> >> Basically the output of >> >> ldd `which lilypond` >> >> should be sufficient for answering this question if you have no clue >> >> what I am talking about. >> >> >> -- >> >> David Kastrup > > Output of ldd `which lilypond`: > > linux-vdso.so.1 (0x7ffd29e4c000) > libdl.so.2 => /usr/lib/libdl.so.2 (0x7f47a901a000) > libguile.so.17 => /usr/lib/libguile.so.17 (0x7f47a8d1d000) [...] 64bit Linux, Guile 1.8. That is a combination that really should work. Any chance to be running this under gdb and/or create a backtrace from a core dump? Basically it would be nice to figure out what kind of code this is happening in in order to figure out what kind of memory became collected prematurely. The actual bug unfortunately is not really connected with the code executed at this time: it triggers an indeterminate time before that and the responsible code is code that someone forgot to write. But at least knowing what kind of data structure might be affected would be a kind of clue how to narrow done the missing code. -- David Kastrup -- Well, I don't have any experience with gdb, so I wouldn't know what to do. The strange thing seems to be that, if the score is engraved using Frescobaldi's verbose output ( which has a separate engrave button ), the error doesn't happen. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange error with no traceable cause.
crimsonsunr...@protonmail.com writes: > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ > > On 5 June 2018 2:33 PM, David Kastrup wrote: > >> crimsonsunr...@protonmail.com writes: >> >> > I'm working on a large score using 2.21.0, parts all separated into >> > >> > different files and such, suddenly, after adding a bar for the 3rd >> > >> > clarinet, this shows up: >> > >> > Parsing... >> > >> > Interpreting music...[8][16]ERROR: In procedure ly:trampoline: >> > >> > ERROR: Wrong type argument in position 3 (expecting Translator): >> > >> > # >> > >> > I have no idea why this is happening. All the other parts add fine >> > >> > but, as soon as the bar is added for that particular instrument, the >> > >> > error shows up. >> > >> > However, if you engrave with verbose output on Frescobaldi >> > >> > enabled...the error doesn't show up. Disable that and do normal >> > >> > engraving...Same error. >> > >> > Any ideas on what's causing it or it might be a Fescobaldi bug? >> >> This is an error in the internals of the memory organization of >> >> LilyPond. Which platform are you using this on, and which version of >> >> Guile has been compiled into it? >> >> Basically the output of >> >> ldd `which lilypond` >> >> should be sufficient for answering this question if you have no clue >> >> what I am talking about. >> >> >> -- >> >> David Kastrup > > Output of ldd `which lilypond`: > > linux-vdso.so.1 (0x7ffd29e4c000) > libdl.so.2 => /usr/lib/libdl.so.2 (0x7f47a901a000) > libguile.so.17 => /usr/lib/libguile.so.17 (0x7f47a8d1d000) [...] 64bit Linux, Guile 1.8. That is a combination that really should work. Any chance to be running this under gdb and/or create a backtrace from a core dump? Basically it would be nice to figure out what kind of code this is happening in in order to figure out what kind of memory became collected prematurely. The actual bug unfortunately is not really connected with the code executed at this time: it triggers an indeterminate time before that and the responsible code is code that someone forgot to write. But at least knowing what kind of data structure might be affected would be a kind of clue how to narrow done the missing code. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange error with no traceable cause.
Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On 5 June 2018 2:33 PM, David Kastrup wrote: > crimsonsunr...@protonmail.com writes: > > > I'm working on a large score using 2.21.0, parts all separated into > > > > different files and such, suddenly, after adding a bar for the 3rd > > > > clarinet, this shows up: > > > > Parsing... > > > > Interpreting music...[8][16]ERROR: In procedure ly:trampoline: > > > > ERROR: Wrong type argument in position 3 (expecting Translator): > > > > # > > > > I have no idea why this is happening. All the other parts add fine > > > > but, as soon as the bar is added for that particular instrument, the > > > > error shows up. > > > > However, if you engrave with verbose output on Frescobaldi > > > > enabled...the error doesn't show up. Disable that and do normal > > > > engraving...Same error. > > > > Any ideas on what's causing it or it might be a Fescobaldi bug? > > This is an error in the internals of the memory organization of > > LilyPond. Which platform are you using this on, and which version of > > Guile has been compiled into it? > > Basically the output of > > ldd `which lilypond` > > should be sufficient for answering this question if you have no clue > > what I am talking about. > > > -- > > David Kastrup Output of ldd `which lilypond`: linux-vdso.so.1 (0x7ffd29e4c000) libdl.so.2 => /usr/lib/libdl.so.2 (0x7f47a901a000) libguile.so.17 => /usr/lib/libguile.so.17 (0x7f47a8d1d000) libltdl.so.7 => /usr/lib/libltdl.so.7 (0x7f47a8b13000) libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x7f47a88ff000) libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x7f47a86b8000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x7f47a8464000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x7f47a814d000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x7f47a7f0a000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x7f47a7c41000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x7f47a78b8000) libm.so.6 => /usr/lib/libm.so.6 (0x7f47a7523000) libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f47a730b000) libpthread.so.0 => /usr/lib/libpthread.so.0 (0x7f47a70ed000) libc.so.6 => /usr/lib/libc.so.6 (0x7f47a6d31000) /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x7f47a9932000) libgmp.so.10 => /usr/lib/libgmp.so.10 (0x7f47a6a9e000) libcrypt.so.1 => /usr/lib/libcrypt.so.1 (0x7f47a6866000) libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x7f47a65b4000) libthai.so.0 => /usr/lib/libthai.so.0 (0x7f47a63aa000) libfribidi.so.0 => /usr/lib/libfribidi.so.0 (0x7f47a618e000) libffi.so.6 => /usr/lib/libffi.so.6 (0x7f47a5f85000) libpcre.so.1 => /usr/lib/libpcre.so.1 (0x7f47a5d13000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0x7f47a5ae1000) libuuid.so.1 => /usr/lib/libuuid.so.1 (0x7f47a58da000) libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x7f47a56ca000) libpng16.so.16 => /usr/lib/libpng16.so.16 (0x7f47a5494000) libz.so.1 => /usr/lib/libz.so.1 (0x7f47a527d000) libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x7f47a5051000) libdatrie.so.1 => /usr/lib/libdatrie.so.1 (0x7f47a4e49000) I'm running it on Archlinux x64. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange error with no traceable cause.
crimsonsunr...@protonmail.com writes: > I'm working on a large score using 2.21.0, parts all separated into > different files and such, suddenly, after adding a bar for the 3rd > clarinet, this shows up: > > Parsing... > > Interpreting music...[8][16]ERROR: In procedure ly:trampoline: > > ERROR: Wrong type argument in position 3 (expecting Translator): > # > > I have no idea why this is happening. All the other parts add fine > but, as soon as the bar is added for that particular instrument, the > error shows up. > > However, if you engrave with verbose output on Frescobaldi > enabled...the error doesn't show up. Disable that and do normal > engraving...Same error. > > Any ideas on what's causing it or it might be a Fescobaldi bug? This is an error in the internals of the memory organization of LilyPond. Which platform are you using this on, and which version of Guile has been compiled into it? Basically the output of ldd `which lilypond` should be sufficient for answering this question if you have no clue what I am talking about. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
