Bug 1805 - relinked Oracle dumps core with glibc-2.1
relinked Oracle dumps core with glibc-2.1
Status: CLOSED DUPLICATE of bug 2187
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 1999-03-25 21:24 EST by Jaroslaw Sosnicki
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-06-16 11:30:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jaroslaw Sosnicki 1999-03-25 21:24:23 EST
There seems to be a major problem with relinking Oracle
8.0.5 and 8.0.5 EE on linux v2.2.x (intel) using
egcs-1.1.2 (glibc-2.1).

8.0.5 instals fine without relinking any of the
 executable and it works
8.0.5 EE forces relinking of all executables, relinking
works fine, when you execute any of the relinked files
it dumps core. Why?,

It looks as there is incompatibilities in the linked in
startup files.

When I relink Oracle with loader flag set to
"-nostartupfiles" I was able to run application but if
dumped core when I exit from exceuted application.

If you want to try it yourself, I used svrmgrl as an

Any ideas on how to fix it?
Comment 1 Cristian Gafton 1999-06-16 11:30:59 EDT
*** This bug has been marked as a duplicate of 2187 ***

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