From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: simple-format causes segfault?
Date: Mon, 08 May 2006 09:12:52 +1000 [thread overview]
Message-ID: <871wv5a0p7.fsf@zip.com.au> (raw)
In-Reply-To: <20060507181518.GB9700@aphex.iro.umontreal.ca> (James Bergstra's message of "Sun, 7 May 2006 14:15:19 -0400")
James Bergstra <james.bergstra@umontreal.ca> writes:
>
> ERROR: In procedure simple-format:
> ERROR: Wrong type argument in position 1: #<freed cell 0x2aaaaae44cb0; GC missed
> a reference>
That'll be something gone bad before the format call.
The only major gremlin in 1.8.0 is I think with shared arrays. If
you're using them and you're brave then you might want to give the cvs
1.8 branch a go.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2006-05-07 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 3:38 simple-format causes segfault? James Bergstra
2006-05-06 22:39 ` Marius Vollmer
2006-05-06 23:20 ` Neil Jerram
2006-05-07 18:15 ` James Bergstra
2006-05-07 23:12 ` Kevin Ryde [this message]
2006-05-09 0:58 ` Rob Browning
2006-05-09 2:35 ` Rob Browning
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=871wv5a0p7.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@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).