On Wed, May 13, 2009 at 3:32 PM, Mark Burton <markb@ordern.com> wrote:
Seriously, something is badly wrong there. Just to confirm, you haven't changed how you invoke mkgmap from the previously successful runs have you?
No, I made no changes to the command line. I am currently recompiling with the patch reversed (this will take some time), but with the same command line options: this appears to be working correctly.
Please try specifying --max-jobs=1 so that only one thread is active and see if it's OK.
I'll reapply the patch and test with --max-jobs=1 (the next time I have a chance).
Also, you should get diagnostic messages at the INFO level that say when the processing of each map starts and ends.
Are these messages sent to STDOUT or do I have to invoke some kind of Java logging to get these diagnostic messages? Cheers.