Bug 22932 - oracle 8.1.6 installer crashes with glibc-2.2-9.i686.rpm
oracle 8.1.6 installer crashes with glibc-2.2-9.i686.rpm
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
7.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-12-28 05:31 EST by pezz@tkwcy.ee
Modified: 2016-11-24 10:25 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-12-28 08:41:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
error message after starting oracle installer script runInstaller (6.82 KB, text/plain)
2000-12-28 05:34 EST, pezz@tkwcy.ee
no flags Details
error message after starting netasst (6.13 KB, text/plain)
2000-12-28 05:35 EST, pezz@tkwcy.ee
no flags Details

  None (edit)
Description pezz@tkwcy.ee 2000-12-28 05:31:16 EST
After updating to glibc-2.2-9.i686.rpm oracle 8.1.6 installer segfaults with 
message 
SIGSEGV received at bfffdc50 in /mnt/cdrom/stage/Components/oracle.swd.jre/1.1.8/1/DataFiles/Expanded/linux/lib/linux/native_threads/libjava.so. Processing terminated
Also it seems that all other oracle's graphical tools crash the same way. All works fine with RedHat7's original glibc-2.1.92-14.
Comment 1 pezz@tkwcy.ee 2000-12-28 05:34:40 EST
Created attachment 6762 [details]
error message after starting oracle installer script runInstaller
Comment 2 pezz@tkwcy.ee 2000-12-28 05:35:53 EST
Created attachment 6763 [details]
error message after starting netasst
Comment 3 Jakub Jelinek 2000-12-28 08:41:36 EST
Have you followed the procedure described in #18391 (basically you have to
make sure all the linking during Oracle install is done against compat-libs
and compat-glibc)?
Comment 4 Jakub Jelinek 2001-01-11 17:53:02 EST
I believe this is the IBM JDK bug which has been worked around
in glibc-2.2-12. If not, please reopen.

Note You need to log in before you can comment on or make changes to this bug.