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: Mon, 22 Jun 2009 10:23:09 -0700 [thread overview]
Message-ID: <20090622171923.M95660@ccrma.Stanford.EDU> (raw)
In-Reply-To: <87skhtpolb.fsf@arudy.ossau.uklinux.net>
> Can you spot some way in which what you are doing
> is different to this?
I believe this is a GC problem; you're doing exactly what I'm doing,
but in a context where the GC is not called. If I place the
skip comment function in its own file, and compile it
with optimization turned off, everything is happy; if
optimization is on (either -O or -O2), it dies. According to
valgrind the problem is in scm_getc -- the SCM_PTAB_ENTRY
pointer "pt" does not point to a valid structure, so the read
and subsuequent write through pt goes off into unallocated
memory. I haven't tracked down the actual problem yet,
but gc-protecting the "port" variable does no good.
next prev parent reply other threads:[~2009-06-22 17:23 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 [this message]
2009-06-22 23:25 ` Neil Jerram
2009-06-23 19:18 ` Bill Schottstaedt
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=20090622171923.M95660@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).