unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Peter TB Brett <peter@peter-b.co.uk>
To: guile-user@gnu.org
Subject: Re: Help needed debugging segfault with Guile 1.8.7
Date: Wed, 10 Nov 2010 21:35:52 +0000	[thread overview]
Message-ID: <m3r5esuaiv.fsf@harrington.peter-b.co.uk> (raw)
In-Reply-To: m3wrol5oxx.fsf@harrington.peter-b.co.uk

[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]

Peter TB Brett <peter@peter-b.co.uk> writes:

> I've added a testsuite for the libgeda Scheme API.  In one commit [2],
> the testsuite succeeds.  In the following commit [3], a test which does
> not touch any of the changed code starts causing a segfault in the Guile
> interpreter.
>
> [snip]
>
> Valgrind / Memcheck wasn't very helpful either.  Is there a way to make
> Guile zero each new heap page it requests before using it in order to
> reduce the number of false positives the gc generates in Memcheck?
>
> In fact, *none* of the ways I've found of running the test without the
> segfault occurring have given me *any* clue as to how to fix it
> "properly".
>
> I'd really appreciate any suggestions that anyone might be able to give
> me on figuring out how I've managed to break things.  At the moment, I'm
> at a complete loss.

So far, as far as I can tell the problem is due to freelist corruption
in the garbage collector, and I'm not sufficiently au fait with Guile
internals to be able to diagnose what's going on.  Is this a known
issue?

                              Peter


-- 
Peter Brett <peter@peter-b.co.uk>
Remote Sensing Research Group
Surrey Space Centre

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-11-10 21:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 12:43 Help needed debugging segfault with Guile 1.8.7 Peter TB Brett
2010-11-10 21:35 ` Peter TB Brett [this message]
2010-11-11 10:52   ` Peter Brett
2010-11-11 12:37     ` Thien-Thi Nguyen
2010-11-11 14:22       ` Peter Brett
2010-11-28 11:38         ` Neil Jerram
2010-11-28 17:21           ` Linas Vepstas
2010-11-30 19:56             ` Peter TB Brett
2010-12-01 19:48               ` Andy Wingo
2010-11-30 19:43           ` Peter TB Brett
2010-12-01 13:46             ` Ludovic Courtès
2010-12-03  7:52               ` Peter TB Brett
2010-11-11  8:22 ` rixed
2010-11-11  8:33 ` Neil Jerram
2010-11-11 13:30 ` Ludovic Courtès

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=m3r5esuaiv.fsf@harrington.peter-b.co.uk \
    --to=peter@peter-b.co.uk \
    --cc=guile-user@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).