unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: David Kastrup <dak@gnu.org>
Cc: 19883@debbugs.gnu.org
Subject: bug#19883: Correction for backtrace
Date: Wed, 25 Feb 2015 23:16:15 +0100	[thread overview]
Message-ID: <87twy91vtc.fsf@gnu.org> (raw)
In-Reply-To: <873865n2rr.fsf@fencepost.gnu.org> (David Kastrup's message of "Mon, 16 Feb 2015 19:13:12 +0100")

David Kastrup <dak@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’.





  reply	other threads:[~2015-02-25 22:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87mvieh7mu.fsf@gnu.org>
2015-02-16 16:41 ` bug#19883: Smob's mark_smob has become unreliable in Guile 2.x David Kastrup
2015-02-16 18:13   ` bug#19883: Correction for backtrace David Kastrup
2015-02-25 22:16     ` Ludovic Courtès [this message]
2015-02-25 23:17       ` David Kastrup
2015-02-26 11:35         ` Ludovic Courtès
2015-02-26 12:32           ` David Kastrup
2015-02-26 14:03             ` Ludovic Courtès
2015-02-26 15:30               ` David Kastrup
2015-02-26 18:15                 ` Ludovic Courtès
2015-02-26 19:25                   ` David Kastrup
2015-02-27  9:55                     ` Ludovic Courtès
2015-02-27 10:18                       ` David Kastrup
2016-06-23  9:50                 ` Andy Wingo
2016-06-23 10:36                   ` Andy Wingo
2016-06-23 13:13                     ` Ludovic Courtès
2016-06-23 13:12                   ` Ludovic Courtès
2015-03-01  6:51   ` bug#19883: Smob's mark_smob has become unreliable in Guile 2.x Mark H Weaver
2015-03-01 10:09     ` David Kastrup
2015-03-01 17:02       ` Mark H Weaver
2015-03-01 18:38         ` David Kastrup
2015-03-01 15:00     ` David Kastrup
2016-10-09  7:51   ` bug#19883: The “finalized” SMOB type Artyom Poptsov
     [not found] ` <87vax2klj6.fsf@elephant.savannah>
     [not found]   ` <87fuo5hc88.fsf@gnu.org>
2016-10-09 19:00     ` Artyom Poptsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87twy91vtc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=19883@debbugs.gnu.org \
    --cc=dak@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).