(so) Missing encoding conversion in handleSocketError

XMLWordPrintable

    • b89
    • generic, x86, sparc
    • solaris, solaris_10, windows_xp

        It appears that an encoding conversion is missing when the function handleSocketError in src/solaris/native/sun/nio/ch/Net.c obtains a string from the C library function strerror and then passes it on to the JNI utility JNU_ThrowByNameWithLastError. C library functions use the native encoding of the current locale, e.g., EUC-JP for Japanese, while JNI functions generally expect Java-modified UTF-8.

              Assignee:
              Xueming Shen
              Reporter:
              Norbert Lindenberg (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: