From: Anand Mohanadoss <anand108@gmail.com>
To: linasvepstas@gmail.com, "Ludovic Courtès" <ludo@gnu.org>,
19180@debbugs.gnu.org
Subject: bug#19180: guile bug#19180: vacuum_weak_hash_table error
Date: Mon, 8 Dec 2014 13:04:30 +0530 [thread overview]
Message-ID: <CAFNjtaC42BrYohB-ygskUvsDgZMsxG7QJAfLK6Vt-BHnbnEotg@mail.gmail.com> (raw)
In-Reply-To: <CAHrUA3554+87CVKsW2OT+-roVeyK4sE+xyDPaGf4ar5fAWQ2+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
Dear Linas,
Thank you so much! I did indeed miss your earlier responses and I
appreciate your reaching out to me!
I downloaded the current guile code in git and will give it a try. But,
given that this is not a stable release, I am not sure if we can really use
it for our purposes.
Do you or Ludovic know when a stable 2.2 version will be released? From
stability point of you, would it be better to use a patched version of
2.0.11 that handles the case we noticed (e.g. don't attempt to remove items
from hash table if len = 0)?
Thanks,
Anand
On Sun, Dec 7, 2014 at 7:22 AM, Linas Vepstas <linasvepstas@gmail.com>
wrote:
> emailing you directly, in case you did not see it:
>
> I've seen the same bug; I tried to apply Ludo's patch, and discovered that
> the current guile code, in git, no longer even has the
> scm_fixup_weak_alist or the vacuum_weak_hash_table calls anywhere in
> them. Also .. my version of the bug goes away.
>
> The code in git seems to be guile-2.2, which has not yet been released --
> so your mileage may vary.. but you certainly won't get that error print
> message any more.
>
> -- Linas
>
[-- Attachment #2: Type: text/html, Size: 1676 bytes --]
next parent reply other threads:[~2014-12-08 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHrUA3554+87CVKsW2OT+-roVeyK4sE+xyDPaGf4ar5fAWQ2+Q@mail.gmail.com>
2014-12-08 7:34 ` Anand Mohanadoss [this message]
2014-12-08 9:34 ` bug#19180: guile bug#19180: vacuum_weak_hash_table error Ludovic Courtès
2014-12-15 6:36 ` Anand Mohanadoss
2016-06-22 14:55 ` Andy Wingo
2016-06-22 15:43 ` Anand Mohanadoss
2016-06-22 21:11 ` Linas Vepstas
2016-06-22 21:33 ` Andy Wingo
2016-06-23 4:24 ` Anand Mohanadoss
2016-07-12 7:32 ` 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=CAFNjtaC42BrYohB-ygskUvsDgZMsxG7QJAfLK6Vt-BHnbnEotg@mail.gmail.com \
--to=anand108@gmail.com \
--cc=19180@debbugs.gnu.org \
--cc=linasvepstas@gmail.com \
--cc=ludo@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).