juniversalchardet-1.0.3_binary-dist-2008-06-23 always returns 'null' charset on some undetermined systems/jvm combinations, but works after rebuild

[GoogleCodeExporter]

What steps will reproduce the problem?
    1. Try charset detection of a file, using the sample code from the homepage.

What is the expected output? What do you see instead?
    Expected: the detected charset (WINDOWS-1252, UTF-8)
    Instead: null

What version of the product are you using? On what operating system?
    Using the Jul 23, 2008 binary of juniversalchardet 1.0.3, SHA1=591d72211acc0b909b79c840e0b3ed9a0982d807
    Problem appeared on:
        a. A x64 Windows Server 2008 R2 server with Java 1.6.0_43
        b. A x64 Windows 7 workstation with Java 1.6.0_43
    Problem did not appear (detection worked flawlessly) on:
        c. Another x64 Windows 7 workstation with Java 1.6.0_43

Please provide any additional information below.
    In order to understand the issue, I ended up re-building the .jar with the debug=true <javac> option. Which of course did let me properly debug like expected, but also solved my problem: now detection worked on machines a and b! That seemed strange, so I rolled back my changes to build.xml, re-launched the compile & dist Ant tasks, and ta-da, it works.

--> One some systems/jvm combinations, it seems the binary build on Jul 23, 
2008 doesn't work and always returns null.

--> Being just a user of the library who barely understands the flow of the 
detection, I failed to understand what went wrong and where and cannot be more 
precise. Feel free to ask for trace information.

--> Maybe publishing a re-compiled version on the website would be a good idea? 
Mine is attached, compiled with Java 1.6.0_43 and Ant 1.9.0 on my machine 'a' 
(x64 Windows Server 2008 R2 server with Java 1.6.0_43).

Original issue reported on code.google.com by ronan.jo...@gmail.com on 15 Mar 2013 at 6:28

Attachments:

• juniversalchardet-1.0.3.jar