unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
Cc: bug-guile@gnu.org
Subject: Re: guile 1.9.0 scm_read_hash_extend gc trouble
Date: Tue, 23 Jun 2009 00:25:48 +0100	[thread overview]
Message-ID: <87bpof7sw3.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <20090622171923.M95660@ccrma.Stanford.EDU> (Bill Schottstaedt's message of "Mon\, 22 Jun 2009 10\:23\:09 -0700")

"Bill Schottstaedt" <bil@ccrma.Stanford.EDU> writes:

> 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.

I tried compiling my test with -O2; unfortunately it's still OK.

>  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.

Do you mean you think that pt has already been freed, or that it was
never valid?

If the former, it sounds like it would be worth trying to prove this,
by adding instrumentation to scm_gc_free that prints the pointer to
stdout whenever what is "port".

You could also instrument (or set a breakpoint on) scm_igc, to
investigate the GC factor.

I'm sorry that we've apparently broken this for you, and that I can't
help more yet...

Regards,
        Neil




  reply	other threads:[~2009-06-22 23:25 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 [this message]
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=87bpof7sw3.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=bil@ccrma.Stanford.EDU \
    --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).