[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#19883: Correction for backtrace
From: |
Ludovic Courtès |
Subject: |
bug#19883: Correction for backtrace |
Date: |
Wed, 25 Feb 2015 23:16:15 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) |
David Kastrup <address@hidden> 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’.
- bug#19883: Smob's mark_smob has become unreliable in Guile 2.x, David Kastrup, 2015/02/16
- bug#19883: Correction for backtrace, David Kastrup, 2015/02/16
- bug#19883: Correction for backtrace,
Ludovic Courtès <=
- bug#19883: Correction for backtrace, David Kastrup, 2015/02/25
- bug#19883: Correction for backtrace, Ludovic Courtès, 2015/02/26
- bug#19883: Correction for backtrace, David Kastrup, 2015/02/26
- bug#19883: Correction for backtrace, Ludovic Courtès, 2015/02/26
- bug#19883: Correction for backtrace, David Kastrup, 2015/02/26
- bug#19883: Correction for backtrace, Ludovic Courtès, 2015/02/26
- bug#19883: Correction for backtrace, David Kastrup, 2015/02/26
- bug#19883: Correction for backtrace, Ludovic Courtès, 2015/02/27
- bug#19883: Correction for backtrace, David Kastrup, 2015/02/27