From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: Mysterious bug in master
Date: Sun, 11 Jan 2015 13:30:03 +0100 [thread overview]
Message-ID: <CAGua6m3Hk9KcumHi80ANAx1ZwUOPGad_6mSbnw8zLvuCuquJ1Q@mail.gmail.com> (raw)
In-Reply-To: <CAGua6m2nRjSiFB8-se9r8DSMMgXBxK=4-KsKJxSkaFmi8GBVzg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2545 bytes --]
I did investigate this further,
It looks like a gc bug that tag for hashtable is replaced by #f and
therefore you get (#f . #(() ....))
I did run this several times and sometimes it ran fine and sometimes you
got this issue.
Is there any specific versions of the gc that must be used and is demanded
by guile-2.1 master?
Regards
Stefan
On Sat, Jan 10, 2015 at 5:30 PM, Stefan Israelsson Tampe <
stefan.itampe@gmail.com> wrote:
> Hi, esp. wingo
>
> Here is the defenition and uses of *freeze-map* in my file parse.scm,
>
> (define *freeze-map* (make-fluid (make-hash-table)))
> (define (clear-tokens)
> (fluid-set! *freeze-map* (make-hash-table)))
> (clear-tokens)
>
> (let ((val (hash-ref (pk 'freeze (fluid-ref *freeze-map*))
> (cons* N M tok) #f))
>
> ...)
>
> (hash-set! (fluid-ref *freeze-map*)
> (cons* n m tok) (list X XL N M XX ...
> val2)))
>
> (hash-set! (fluid-ref *freeze-map*)
> (cons* n m tok) val2))
>
> (with-fluids ((*freeze-map* (pk 22 (fluid-ref *freeze-map*))))
> (clear-tokens)
>
>
> sometimes this fails sometimes not when using the code e.g.
> ;;; (freeze (#f . #(() () () () () () () () () () () () () () () () () ()
> () () () () () () () () () () () () ())))
> ERROR: In procedure hash-ref:
>
> Sometimes when I comile with a change of whitespaces I can make the code
> run else I get
> this mysterious error. This is a clue that there might be a bug in 2.1,
> guile-log is a bit naughty
> so I don't want to put the blame on guile, just hint that there might be a
> fundamental bug in there
>
> I tracked it down to the clear-tokens function, that ,x clear-tokens
> assembly is
> 0 (assert-nargs-ee/locals 1 3) ;; 0 args, 3 locals at
> logic/guile-log/parser.scm:64:0
> 1 (toplevel-box 0 57143 36139 36137 #t);; `*freeze-map*'
> 6 (box-ref 0 0)
> 7 (toplevel-box 1 57139 36133 36121 #t);; `make-hash-table'
> 12 (box-ref 3 1)
> 13 (call 3 1) at
> logic/guile-log/parser.scm:65:27
> 15 (receive 1 3 4)
> 17 (module-box 2 41407 34463 41405 #t);; `(@@ (guile) fluid-set!)'
> 22 (box-ref 2 2) at
> logic/guile-log/parser.scm:65:2
> 23 (mov 3 2)
> 24 (mov 2 1)
> 25 (mov 1 0)
> 26 (mov 0 3)
> 27 (tail-call 3)
>
> I'm wondering if the receive value 4 is protected by the frame that is the
> return of make-hash-table.
>
> Regards
> Stefan
>
>
>
[-- Attachment #2: Type: text/html, Size: 4014 bytes --]
prev parent reply other threads:[~2015-01-11 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 16:30 Mysterious bug in master Stefan Israelsson Tampe
2015-01-11 12:30 ` Stefan Israelsson Tampe [this message]
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=CAGua6m3Hk9KcumHi80ANAx1ZwUOPGad_6mSbnw8zLvuCuquJ1Q@mail.gmail.com \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@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).