From: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: guile 1.9.0 scm_read_hash_extend gc trouble
Date: Tue, 23 Jun 2009 12:18:16 -0700 [thread overview]
Message-ID: <20090623191142.M93181@ccrma.Stanford.EDU> (raw)
In-Reply-To: <87bpof7sw3.fsf@arudy.ossau.uklinux.net>
This is trickier than I thought -- it's not the GC after all. In my configure
script for Snd, autoconf defines _FILE_OFFSET_BITS to 64 if large files are implemented.
The config.h "include" precedes everything else. When scm_getc is called
within guile, it thinks sizeof(scm_t_port) is 92. Everything is fine until
my skip comment procedure is called (with this 92 byte struct) -- it
thinks the scm_t_port size is 104, and fields like rw_active (in scm_getc
which is apparently expanded inline) are not where it expects them to be!
If I undef _FILE_OFFSET_BITS, both agree on the struct size, and there
is no problem.
next prev parent reply other threads:[~2009-06-23 19:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 12:10 guile 1.9.0 scm_read_hash_extend gc trouble Bill Schottstaedt
2009-06-21 15:34 ` Neil Jerram
2009-06-21 15:56 ` Neil Jerram
2009-06-22 17:23 ` Bill Schottstaedt
2009-06-22 23:25 ` Neil Jerram
2009-06-23 19:18 ` Bill Schottstaedt [this message]
2009-06-23 23:07 ` Ludovic Courtès
2009-06-27 21:53 ` Neil Jerram
2009-06-27 23:42 ` Ludovic Courtès
2009-06-29 15:02 ` Ludovic Courtès
2009-06-29 19:18 ` Neil Jerram
2009-06-24 10:19 ` Bill Schottstaedt
2009-06-22 8:50 ` Thien-Thi Nguyen
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=20090623191142.M93181@ccrma.Stanford.EDU \
--to=bil@ccrma.stanford.edu \
--cc=bug-guile@gnu.org \
--cc=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).