From: Andy Wingo <wingo@pobox.com>
Subject: Re: Segmentation fault in CVS
Date: Wed, 14 Dec 2005 11:20:47 +0100 [thread overview]
Message-ID: <1134555647.13759.176.camel@localhost.localdomain> (raw)
In-Reply-To: <873bkwy2fs.fsf@ossau.uklinux.net>
Hi,
On Tue, 2005-12-13 at 23:58 +0000, Neil Jerram wrote:
> read_without_guile_data *data = (read_without_guile_data *)data;
Didn't fix the issue for me, same symptoms. Can't run pre-inst-guile; it
gives me:
(pygst gst) wingo@videoscale:~/src/guile/guile-core$ ./pre-inst-guile
ERROR: In procedure memoization:
ERROR: Bad binding #<freed cell 0x2aaaabc6de30; GC missed a reference>
in expression [...]
Regards,
--
Andy Wingo
http://wingolog.org/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-12-14 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 20:01 Segmentation fault in CVS Neil Jerram
[not found] ` <4397470B.3070505@gnu.org>
2005-12-09 14:09 ` Neil Jerram
2005-12-13 23:58 ` Neil Jerram
2005-12-14 10:20 ` Andy Wingo [this message]
2005-12-14 23:31 ` Neil Jerram
2005-12-14 21:49 ` Marius Vollmer
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=1134555647.13759.176.camel@localhost.localdomain \
--to=wingo@pobox.com \
/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).