From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: bug-guile@gnu.org, jantien@xs4all.nl, guile-devel@gnu.org,
fodber@interware.hu
Subject: Re: Serious GC bug in GUILE 1.6 CVS
Date: Thu, 9 Sep 2004 01:15:43 +0200 [thread overview]
Message-ID: <16703.37535.594397.357127@byrd.xs4all.nl> (raw)
In-Reply-To: <lj4qmadqwq.fsf@troy.dt.e-technik.uni-dortmund.de>
marius.vollmer@uni-dortmund.de writes:
> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
> > Compile GUILE with
> >
> > #define SCM_DEBUG_CELL_ACCESSES 1
> >
> > in config.h. Then apply this patch
> >
> > + (set-debug-cell-accesses! 5000)
> >
> > then compilation bombs out with:
>
> I have found the bug. init_heap_seg was using SCM_SET_CELL_TYPE to
> initialize fresh memory to 'free cells', but with DEBUG_CELL_ACCESSES,
> SCM_SET_CELL_TYPE could run a GC, which might see the half initialized
> heap segment during conservative scanning and would access
> uninitialozed memory which caused it to fail.
>
> I have fixed this by using the new macro SCM_SET_FREE_CELL_TYPE, which
> does no checking.
Hmm... That's unfortunate. We have reports of GC flakiness with 1.6
on Cygwin. This means that there's still another bug lurking.
--
Han-Wen Nienhuys | hanwen@xs4all.nl | http://www.xs4all.nl/~hanwen
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2004-09-08 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 21:27 Serious GC bug in GUILE 1.6 CVS Han-Wen Nienhuys
2004-09-07 15:45 ` Marius Vollmer
2004-09-08 23:15 ` Han-Wen Nienhuys [this message]
2004-09-08 23:27 ` Marius Vollmer
2004-09-09 22:32 ` Neil Jerram
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=16703.37535.594397.357127@byrd.xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=bug-guile@gnu.org \
--cc=fodber@interware.hu \
--cc=guile-devel@gnu.org \
--cc=jantien@xs4all.nl \
/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).