Parsed object should be dead

2021-02-06 Thread Dan Eble
Did something change in the past couple of weeks to make "Parsed object should be dead" messages more likely? Now that I've turned from documentation back to development, they seem to be getting in my way much more than they used to. This stan

Parsed object should be dead

2011-05-30 Thread m...@apollinemike.com
Hey all, I've been getting this from LilyPond recently: programming error: Parsed object should be dead: static scm_unused_struct* Prob::mark_smob(scm_unused_struct*) continuing, cross fingers Is anyone else getting this too? Cheer

Parsed object should be dead

2012-03-27 Thread m...@apollinemike.com
I'm getting a lot of: programming error: Parsed object should be dead: static scm_unused_struct* Prob::mark_smob(scm_unused_struct*) continuing, cross fingers from current master. Is anyone else having this problem? Cheers, MS ___ lilypond-

Re: Parsed object should be dead

2021-02-06 Thread Jonas Hahnfeld
Am Samstag, dem 06.02.2021 um 13:33 -0500 schrieb Dan Eble: > Did something change in the past couple of weeks to make "Parsed > object should be dead" messages more likely? Now that I've turned > from documentation back to development, they seem to be getting in my > w

Re: Parsed object should be dead

2021-02-07 Thread Han-Wen Nienhuys
On Sat, Feb 6, 2021 at 7:33 PM Dan Eble wrote: > Did something change in the past couple of weeks to make "Parsed object > should be dead" messages more likely? Now that I've turned from > documentation back to development, they seem to be getting in my way much

Re: Parsed object should be dead

2021-02-08 Thread Jonas Hahnfeld
Am Sonntag, dem 07.02.2021 um 23:16 +0100 schrieb Han-Wen Nienhuys: > On Sat, Feb 6, 2021 at 7:33 PM Dan Eble wrote: > > > Did something change in the past couple of weeks to make "Parsed object > > should be dead" messages more likely? Now that I've turn

Re: Parsed object should be dead

2011-05-30 Thread Werner LEMBERG
> I've been getting this from LilyPond recently: > > programming error: Parsed object should be dead: static scm_unused_struct* > Prob::mark_smob(scm_unused_struct*) > continuing, cross fingers > > Is anyone else getting this too? I'm getting this all the

Re: Parsed object should be dead

2011-05-30 Thread m...@apollinemike.com
On May 31, 2011, at 6:23 AM, Werner LEMBERG wrote: >> I've been getting this from LilyPond recently: >> >> programming error: Parsed object should be dead: static scm_unused_struct* >> Prob::mark_smob(scm_unused_struct*) >> continuing, cross fingers >

Re: Parsed object should be dead

2011-06-01 Thread Patrick McCarty
Hi Mike, On Mon, May 30, 2011 at 4:08 PM, m...@apollinemike.com wrote: > > I've been getting this from LilyPond recently: > > programming error: Parsed object should be dead: static scm_unused_struct* > Prob::mark_smob(scm_unused_struct*) > continuing, cross fingers

Re: Parsed object should be dead

2011-06-09 Thread Han-Wen Nienhuys
On Mon, May 30, 2011 at 8:08 PM, m...@apollinemike.com wrote: > Hey all, > > I've been getting this from LilyPond recently: > > programming error: Parsed object should be dead: static scm_unused_struct* > Prob::mark_smob(scm_unused_struct*) > continuing, cross fingers

Re: Parsed object should be dead

2012-03-27 Thread David Kastrup
"m...@apollinemike.com" writes: > I'm getting a lot of: > > programming error: Parsed object should be dead: static > scm_unused_struct* Prob::mark_smob(scm_unused_struct*) > continuing, cross fingers > > from current master. Is anyone else having this pr

Re: Parsed object should be dead

2012-03-27 Thread David Kastrup
David Kastrup writes: > "m...@apollinemike.com" writes: > >> I'm getting a lot of: >> >> programming error: Parsed object should be dead: static >> scm_unused_struct* Prob::mark_smob(scm_unused_struct*) >> continuing, cross fingers >> &g

Re: Parsed object should be dead

2012-03-27 Thread David Kastrup
"m...@apollinemike.com" writes: > I'm getting a lot of: > > programming error: Parsed object should be dead: static > scm_unused_struct* Prob::mark_smob(scm_unused_struct*) > continuing, cross fingers > > from current master. Is anyone else having thi

"Parsed object should be dead" with LilyDev 3

2014-10-25 Thread Dan Eble
Does anyone else see a lot of “Parsed object should be dead” programming errors in the regression test logs? — Dan ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: "Parsed object should be dead" with LilyDev 3

2014-10-26 Thread James Lowe
On 26/10/14 02:49, Dan Eble wrote: > Does anyone else see a lot of “Parsed object should be dead” programming > errors in the regression test logs? > — > Dan As another example: https://code.google.com/p/lilypond/issues/detail?id=4156 See comment #5 onwards. I think you're

Re: "Parsed object should be dead" with LilyDev 3

2014-10-26 Thread David Kastrup
Dan Eble writes: > Does anyone else see a lot of “Parsed object should be dead” > programming errors in the regression test logs? They occur sometimes. If they are a regular, they might point to a problem. -- David Kastrup ___ lilypond

Re: "Parsed object should be dead" with LilyDev 3

2014-10-26 Thread Dan Eble
On Oct 26, 2014, at 08:35 , David Kastrup wrote: > Dan Eble writes: > >> Does anyone else see a lot of “Parsed object should be dead” >> programming errors in the regression test logs? > > They occur sometimes. If they are a regular, they might point to a > problem.

Re: "Parsed object should be dead" with LilyDev 3

2014-10-26 Thread Werner LEMBERG
>>> Does anyone else see a lot of “Parsed object should be dead” >>> programming errors in the regression test logs? >> >> They occur sometimes. If they are a regular, they might point to a >> problem. > > OK, thanks. The reason I noticed them is that

Re: "Parsed object should be dead" with LilyDev 3

2014-10-26 Thread David Kastrup
Werner LEMBERG writes: >>>> Does anyone else see a lot of “Parsed object should be dead” >>>> programming errors in the regression test logs? >>> >>> They occur sometimes. If they are a regular, they might point to a >>> problem. >> &g

Avoid "Parsed object should be dead" message from issue 4505 (issue 258030043 by d...@gnu.org)

2015-07-29 Thread lemzwerg
LGTM https://codereview.appspot.com/258030043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel