lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dawid Weiss <>
Subject Re: Possible problem with RAMDirectory; tips please
Date Sat, 06 Apr 2013 19:13:05 GMT
Ok, thanks.

What I do in such circumstances is apply an aspect (aspectj) that logs
(for every thread) every entry/exit from a block of code I'm
interested in (package, class, etc.) and then run the two differing
configurations. Then I simply diff the outputs using Araxis Merge --
this is typically enough to tell what execution paths are different
and lets you set up a trap to analyze the problem at its source
(diverging paths).

Yes, it requires some aspectj expertise and getting to know this may
exceed what you need :) Create an issue though and provide a patch,
perhaps me or somebody else will know what's going on.


On Sat, Apr 6, 2013 at 9:03 PM, David Smiley (
<> wrote:
> I'll try to make a version of the test that is unrandomized -- I'll index the
> exact shapes needed and query for the specific shape using the right
> algorithm.  And at that point, I'll try and reduce it.  Simon's right; I'm
> looking for debugging tips/strategy advise.  I find it pretty odd that my
> test will fail for a particular directory but not others (in the right
> circumstances -- i.e. the specific shapes etc.).  That is suspicious -- it
> has me wondering if the bug is perhaps not in my code after all since I
> don't know what my code (or anyone's Lucene code for that matter) could
> possibly be doing that would make the outcome dependent on the directory
> implementation.
> ~ David
> -----
>  Author:
> --
> View this message in context:
> Sent from the Lucene - Java Developer mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message