After I upgraded to the 19-Dec-2000 glibc 2.2, my IBM Java 1.1.8 reports a segmentation violation SIGSEGV on startup. Was working fine just before update. Looks like this was fixed in the 2.1.xx stream before.
This seems to be a bug in locale handling, as unsetting LANG it works fine.
This seems to be a bug in locale handling. If you clear LANG enveronment variable, it works fine.
Yes, but a locale handling bug in IBM Java. libjava.so's java_lang_System_initProperties function does approximately (don't have source, so this is just what I saw under debugger): char *p = setlocale(LC_CTYPE, ""), *q; setlocale(LC_ALL, p); q = strchr(p, '_'); At least according to my reading of http://www.opennc.org/onlinepubs/7908799/xsh/setlocale.html this is wrong: The string returned by setlocale() is such that a subsequent call with that string and its associated category will restore that part of the program's locale. The string returned must not be modified by the program, but may be overwritten by a subsequent call to setlocale(). (last sentence does not speak about setlocale with the same category). I'll see what I can do here (either prepare a glibc patch that it will use the same string in this case or talk to IBM).
Hopefully a glibc patch - IBM 1.1.8 is what Oracle 8.1.x uses for most things and it now bombs on installing 817...
Nope, see http://sources.redhat.com/ml/libc-hacker/2001-01/msg00002.htmlhttp://sources.redhat.com/ml/libc-hacker/2001-01/msg00002.html and the following thread. So, I'm going to mail the IBM Linux Java newsgroup today, unless you tell me better contacts within IBM. I can try to hack up a workaround LD_PRELOAD library for the time being but IBM JDK should be fixed ASAP (apparently the code has 2 different bugs, not only one, but only one causes it not to work with glibc-2.2-9 (and the upcoming glibc 2.2.1 release)) or put one of the patches into glibc errata rpms (but that would only delay breakage with later glibc releases (and other distributions)).
I've included temporary workaround for this into our glibc, just stay assured that it will break on all other distributions with glibc-2.2 and above.
Just to confirm that the w/a works in case of the Oracle 817 installer... thanks. By the time newer glibc is out I hope to be on Oracle 90x :)
Thanks for finding and providing a solution to this problem. As of April 2004, IBM is _still_ shipping the broken version as their free Linux download (DB2 Connection Personal Edition) and with your hint re LANG I was, after two days, able to install onto Fedora the DB2 software using IBM's Java-based DB2 installer. Whew! I just wanted to add to the historical record for those who stumble upon this issue after me.