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 turned
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
&g
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
> way mu
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 stands ou
LGTM
https://codereview.appspot.com/258030043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
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 hitting the kind
Dan Eble d...@faithful.be 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
On Oct 26, 2014, at 08:35 , David Kastrup d...@gnu.org wrote:
Dan Eble d...@faithful.be 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.
OK
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 they were not regular.
For the record, I never saw them
Werner LEMBERG w...@gnu.org 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.
OK, thanks. The reason I noticed them is that they were not regular
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
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-devel
m...@apollinemike.com 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 problem?
I have not gotten
David Kastrup d...@gnu.org writes:
m...@apollinemike.com 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
m...@apollinemike.com 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 problem?
URL:http
On Mon, May 30, 2011 at 8:08 PM, m...@apollinemike.com
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
Is anyone
Hi Mike,
On Mon, May 30, 2011 at 4:08 PM, m...@apollinemike.com
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
This usually
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
Is anyone else getting this too?
I'm getting
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?
Cheers,
MS
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 time if I build with --disable-optimising
20 matches
Mail list logo
