Null Pointer Exception in FSIndexInput::close causing abort?

>> Ok, gcc 3.4.5 doesn't get the abort, so I guess
there's a regression 
>> in the 4.1 tree.  Thanks for the idea; I don't
really have a 
>> reasonable test case for demonstrating this bug
yet, but I'll work on 
>> it.  Thanks!
>
> I'm not too surprised, I've had little luck with gcj
4.x so far.
>

Searching for nullpointer gcj abort, I found a posting from
April, 2000 
that caused aborts rather than null pointer exceptions. 
Well, it still 
seems to work today   I'll be
posting this on the gcj list as soon as 
I verify that it's still a bug in the current svn head.

The fatal code:

public class NullPointer
{
   private int i = 5;

   public static void main(String[] args)
   {
     try
     {
       new NullPointer().foo(null);
     }
     catch (NullPointerException x)
     {
       System.out.println(x);
     }
   }

   void foo(NullPointer e)
   {
     e.i += 4;
   };
}

I guess this is just a bit of a warning to PyLucene users
who are using 
the 4.1 versions of gcc; be careful 

_______________________________________________
pylucene-dev mailing list
pylucene-devosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/pylu
cene-dev