GNU bug report logs - #19883
Smob's mark_smob has become unreliable in Guile 2.x

Previous Next

Full log

Message #11 received at 19883 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: David Kastrup <dak <at> gnu.org>
Cc: 19883 <at> debbugs.gnu.org
Subject: Re: bug#19883: Correction for backtrace
Date: Wed, 25 Feb 2015 23:16:15 +0100

David Kastrup <dak <at> gnu.org> skribis:

> This is embarrassing: I used the wrong executable in connection with the
> core dump.  With the matching executable, the coredump makes a lot more
> sense:
>
> #0  0x00000000 in ?? ()
> #1  0x0804aee0 in Smob_base<Family>::mark_trampoline (arg=0x9fbb000)
>     at smobs.tcc:34
> #2  0xb761b2da in ?? () from /usr/lib/libguile-2.0.so.22
> #3  0xb72751f8 in GC_mark_from () from /usr/lib/i386-linux-gnu/libgc.so.1

Could you try commenting out all the SMOB mark functions in LilyPond?

This doesn’t fix the bug, of course, but it’s probably a good
workaround: user-provided mark functions are not needed in Guile 2.0
since libgc scans the whole heap for live pointers.

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.