unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Anand Mohanadoss <anand108@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 19180@debbugs.gnu.org
Subject: bug#19180: vacuum_weak_hash_table error
Date: Mon, 1 Dec 2014 18:13:25 +0530	[thread overview]
Message-ID: <CAFNjtaAedAzrM1cJz3s+a9TU8eHWmSXgL26da7OCLFDPQL_Y4A@mail.gmail.com> (raw)
In-Reply-To: <87ppc78dry.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]

Dear Ludovic,

Thank you very much for your help!  Given that the problem happens for me
only while processing huge binary files after around an hour of processing
(and the problem in general is not consistent), I am not sure how to come
up with a reduced test case that would still reproduce the problem.  So, I
would appreciate any help with that.

I was also wondering that given we can reproduce the problem under a
particular circumstance, if we can approach the problem from the other side
- e.g. by making changes on guile side to print information on the hash
table for which the assertion is failing, print stats on this hash table
over a period of time, make changes to hash table code to try to resolve
the problem, etc.

Thanks,
Anand

On Fri, Nov 28, 2014 at 10:26 PM, Ludovic Courtès <ludo@gnu.org> wrote:

> Anand Mohanadoss <anand108@gmail.com> skribis:
>
> > We have observed the following error a few times with guile 2.0.11
> (32-bit)
> > on x86_64 Linux while processing large binary files (1.5GB+) and
> comparing
> > messages contained therein.
> >
> > fish: hashtab.c:137: vacuum_weak_hash_table: Assertion `removed <= len'
> > failed.
>
> [...]
>
> > Given that we can consistently reproduce this problem on a particular
> > system, is there something you would like us to try to find the
> underlying
> > cause of this problem?
>
> Could you try to come up with a reduced test case to reproduce the
> problem?  That would help find out what’s going on.  Let us know if you
> need help to do that.
>
> Thanks for the report!
>
> Ludo’.
>

[-- Attachment #2: Type: text/html, Size: 2071 bytes --]

  reply	other threads:[~2014-12-01 12:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 11:23 bug#19180: vacuum_weak_hash_table error Anand Mohanadoss
2014-11-28 16:56 ` Ludovic Courtès
2014-12-01 12:43   ` Anand Mohanadoss [this message]
2014-12-02 19:47 ` Ludovic Courtès
2014-12-06  8:57   ` Anand Mohanadoss
2014-12-07  1:42   ` Linas Vepstas
2014-12-03 22:46 ` Linas Vepstas

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=CAFNjtaAedAzrM1cJz3s+a9TU8eHWmSXgL26da7OCLFDPQL_Y4A@mail.gmail.com \
    --to=anand108@gmail.com \
    --cc=19180@debbugs.gnu.org \
    --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).