From: "Han-Wen Nienhuys" <hanwenn@gmail.com>
To: "Andy Wingo" <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: Race condition in threading code?
Date: Tue, 26 Aug 2008 21:41:41 -0300 [thread overview]
Message-ID: <f329bf540808261741h2bc1dcf5v664d0a04aaa17d1@mail.gmail.com> (raw)
In-Reply-To: <m3iqtnseza.fsf@pobox.com>
It could be an existing problem that is exposed by the new tighter allocation.
With a larger heap, there are larger intervals between recollection of the heap.
Let me run this through DEBUGINFO when I get the chance.
On Tue, Aug 26, 2008 at 5:23 PM, Andy Wingo <wingo@pobox.com> wrote:
> Hi,
>
> On Sat 16 Aug 2008 11:45, Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
>> Julian Graham escreveu:
>>> Hmmm... I don't recall seeing those when I was writing that test
>>> suite. Just to be clear, were you getting those errors before making
>>> your changes?
>>
>> No, but some very unrelated changes made them go away again.
>
> I still get that error, having merged master into vm. Do you have other
> fixes?
>
> The original error that you had, reflowed:
>
> ERROR: srfi-18.test: thread-start!:
> thread activates only after start
> - arguments: ((syntax-error "memoization"
> "In file ~S, line ~S: ~A ~S in expression ~S."
> ("/home/lilydev/vc/guile/srfi/srfi-18.scm" 135
> "Bad binding" ct
> (let (ct (current-thread))
> #@let (or (hashq-ref thread-exception-handlers ct)
> (hashq-set! thread-exception-handlers ct
> (list initial-handler))))) #f))
>
> Bad binding with an #@let???? This would seem to indicate that a
> memoized cell was not marked, and was then swept/re-used.
>
> Andy
> --
> http://wingolog.org/
>
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2008-08-27 0:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 18:21 Race condition in threading code? Han-Wen Nienhuys
2008-08-16 18:42 ` Julian Graham
2008-08-16 18:45 ` Han-Wen Nienhuys
2008-08-26 20:23 ` Andy Wingo
2008-08-27 0:41 ` Han-Wen Nienhuys [this message]
2008-08-27 2:36 ` Han-Wen Nienhuys
2008-08-27 7:46 ` Ludovic Courtès
2008-08-27 13:14 ` Julian Graham
2008-08-30 23:05 ` Julian Graham
2008-08-31 1:49 ` Han-Wen Nienhuys
2008-08-31 2:54 ` Julian Graham
2008-08-31 13:52 ` Han-Wen Nienhuys
2008-08-31 10:34 ` Ludovic Courtès
2008-08-31 12:58 ` Ludovic Courtès
2008-08-31 15:05 ` Julian Graham
2008-08-31 19:39 ` Ludovic Courtès
2008-09-07 0:12 ` Julian Graham
2008-09-08 12:37 ` Ludovic Courtès
2008-08-31 20:08 ` Ludovic Courtès
2008-08-31 23:59 ` Han-Wen Nienhuys
2008-09-01 8:11 ` Ludovic Courtès
2008-09-01 0:18 ` Han-Wen Nienhuys
2008-09-03 4:56 ` Han-Wen Nienhuys
2008-09-04 18:12 ` Andy Wingo
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=f329bf540808261741h2bc1dcf5v664d0a04aaa17d1@mail.gmail.com \
--to=hanwenn@gmail.com \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
--cc=wingo@pobox.com \
/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).