I’m not sure what to make of this. When starting Vassal 3.1.14, on my Mac, the errorLog shows the following error for a “Bad address”. This does not crash anything, and the application seems to work fine in spite of it.
15 Sep 2010 17:07:44.831 0 – Starting
15 Sep 2010 17:07:44.832 0 – OS Mac OS X
15 Sep 2010 17:07:44.833 0 – Java version 1.6.0_20
15 Sep 2010 17:07:44.833 0 – VASSAL version 3.1.14
15 Sep 2010 17:07:45.439 0 – Manager
15 Sep 2010 17:07:46.642 0 Error 14: Bad address
15 Sep 2010 17:07:46.642 0
I’m not sure what to make of this. When starting Vassal 3.1.14, on my
Mac, the errorLog shows the following error for a “Bad address”. This
does not crash anything, and the application seems to work fine in spite
of it.
15 Sep 2010 17:07:44.831 0 – Starting
15 Sep 2010 17:07:44.832 0 – OS Mac OS X
15 Sep 2010 17:07:44.833 0 – Java version 1.6.0_20
15 Sep 2010 17:07:44.833 0 – VASSAL version 3.1.14
15 Sep 2010 17:07:45.439 0 – Manager
15 Sep 2010 17:07:46.642 0 Error 14: Bad address
15 Sep 2010 17:07:46.642 0
I’ve seen this in a few errorLogs which came from Macs. It’s something
that the JVM or the system is printing to our STDERR (which is redirected
to the log). Google doesn’t seem to know about this error on the Mac; I’ll
ask on the apple-java list.
I’m not sure what to make of this. When starting Vassal 3.1.14, on my
Mac, the errorLog shows the following error for a “Bad address”. This
does not crash anything, and the application seems to work fine in spite
of it.
15 Sep 2010 17:07:44.831 0 – Starting
15 Sep 2010 17:07:44.832 0 – OS Mac OS X
15 Sep 2010 17:07:44.833 0 – Java version 1.6.0_20
15 Sep 2010 17:07:44.833 0 – VASSAL version 3.1.14
15 Sep 2010 17:07:45.439 0 – Manager
15 Sep 2010 17:07:46.642 0 Error 14: Bad address
15 Sep 2010 17:07:46.642 0
I’ve seen this in a few errorLogs which came from Macs. It’s something
that the JVM or the system is printing to our STDERR (which is redirected
to the log). Google doesn’t seem to know about this error on the Mac; I’ll
ask on the apple-java list.
I’ve had no reply about this on java-dev@lists.apple.com, unfortunately.
I suspect that the problem has something to do with sockets, but that’s
only a guess.
I’m not sure what to make of this. When starting Vassal 3.1.14,
on my
Mac, the errorLog shows the following error for a “Bad address”.
This
does not crash anything, and the application seems to work fine in
spite
of it.
15 Sep 2010 17:07:44.831 0 – Starting
15 Sep 2010 17:07:44.832 0 – OS Mac OS X
15 Sep 2010 17:07:44.833 0 – Java version 1.6.0_20
15 Sep 2010 17:07:44.833 0 – VASSAL version 3.1.14
15 Sep 2010 17:07:45.439 0 – Manager
15 Sep 2010 17:07:46.642 0 Error 14: Bad address
15 Sep 2010 17:07:46.642 0
I’ve seen this in a few errorLogs which came from Macs. It’s
something
that the JVM or the system is printing to our STDERR (which is
redirected
to the log). Google doesn’t seem to know about this error on the
Mac; I’ll
ask on the apple-java list.
I’ve had no reply about this on java-dev@lists.apple.com,
unfortunately.
I suspect that the problem has something to do with sockets, but
that’s
only a guess.
Thanks for the update.
I saw your question on the Apple Java list.