From: Neil Jerram <neil@ossau.uklinux.net>
Subject: 1.8 status and 64-bit data corruption
Date: Sun, 26 Mar 2006 14:08:11 +0100 [thread overview]
Message-ID: <87d5g98ibo.fsf@ossau.uklinux.net> (raw)
I believe the only important 1.8 bug still outstanding is the one
which causes Scheme data corruption on 64-bit platforms - and which is
usually enough to cause the build to fail in
snarf-check-and-output-texi.
Is there anything else of equal impact that I've forgotten?
I'm not sure how to proceed with debugging this (or rather with
advising someone else how to debug it, since I don't have a 64-bit box
myself), so does anyone else have ideas? I've been assuming it's a GC
problem, i.e. data which should be marked but isn't for some reason,
but I guess it need not be; it could just be something modifying part
of the Scheme heap by mistake.
Here are references to some of the relevant threads.
http://lists.gnu.org/archive/html/guile-devel/2006-02/msg00044.html
http://lists.gnu.org/archive/html/bug-guile/2006-02/msg00009.html
http://lists.gnu.org/archive/html/bug-guile/2006-02/msg00016.html
http://lists.gnu.org/archive/html/guile-user/2006-03/msg00008.html
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2006-03-26 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 13:08 Neil Jerram [this message]
2006-03-28 20:56 ` 1.8 status and 64-bit data corruption Neil Jerram
2006-03-29 10:07 ` Andy Wingo
-- strict thread matches above, loose matches on Subject: below --
2006-03-29 15:12 Bill Schottstaedt
2006-03-29 15:40 ` Jay Cotton
2006-04-15 12:45 Bill Schottstaedt
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=87d5g98ibo.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
/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).