Bug? inconsistent state after integer overflow

Question

hi there,
im running java 6 se with the latest updates on macosx 10.6.4
i implemented a primality check, which didnt give the right answer in some cases.
several tests with the same input gave me different output, though the used algorithm is deterministic.
i could reduce the code to just a few lines. its attached.
the code gives me unpredictable results
mostly i get 20001 (which is correct), 1, 1025 or 199XX.
only u = 2^31-1 produces this behaviour.
the integer wraparound is a welldefined operation, i think.
so this is a serious bug, isnt it?
public class wtf
     public static void main(String... args)
          for (int i = 0; i < 20; i++)
               work(2147463647, 2147483647);
     static void work(int l, int u)
          int runs = 0;
          for (int i = l; (i <= u) && (i > 0); i++)
               runs++;
          System.out.println(runs);
}

Answer 1

I managed to sort this on my own and here's what I learned in case someone else comes across this issue in the future.
The library was not corrupted, but it was buggy. The lack of any available views caused the paths to go weird as described above. The allitems view was not deleted, however, but it was marked as hidden and had the name removed from it. I was able to recover
this by modifying the properties on the allitems view in the SPList.views collection. Not sure how it happened, but it was an easy fix.
The other issue was me being a newbie with SP. The user had uploaded new files for the list using explorer which appears to initially set them to be checked out. Since they never had a checked in version, they don't appear in any view, in search, etc. but
they are included in the SPList.ItemCount property. This resulted in a seemingly "empty" document library with files in it.
I hope this helps the next person to come along with a similar problem. Serious pain to figure this out, but I got a lot of good experience with the SP PowerShell environment, so it had a bit of a silver lining.