Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 63705 - undefined symbol: atexit
undefined symbol: atexit
Product: Red Hat Public Beta
Classification: Retired
Component: glibc (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-04-17 12:42 EDT by Need Real Name
Modified: 2016-11-24 10:28 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-04-18 11:41:48 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 Need Real Name 2002-04-17 12:42:54 EDT
Description of Problem:
Vmware workstation 3.1 and RealPlayer 8 both exit immediately with the following
error message:
 undefined symbol: atexit

Version-Release number of selected component (if applicable):

How Reproducible:
Simply try to run vmware or realplayer 8

Steps to Reproduce:
1. execute realplayer version 8
2. execute vmware 3.1

Actual Results:
/usr/lib/RealPlayer8/realplay: relocation error:
/usr/lib/RealPlayer8/Codecs/cook.so.6.0: undefined symbol: atexit

vmware: relocation error: vmware: undefined symbol: atexit

Expected Results:
RealPlayer Window to open.
Vmware window to open.

Additional Information:
If I revert back to glibc-2.2.5-30 I don't get the error.
Comment 1 Jakub Jelinek 2002-04-18 10:28:12 EDT
Fixed in glibc-2.2.5-32.
Comment 2 Need Real Name 2002-04-18 11:41:43 EDT
 rpm -qa | grep glibc
$ /usr/lib/RealPlayer8/realplay
/usr/lib/RealPlayer8/realplay: relocation error:
/usr/lib/RealPlayer8/Codecs/cook.so.6.0: undefined symbol: atexit
$ vmware
vmware: relocation error: vmware: undefined symbol: atexit

As you can see from above the problem "is not" fixed in glibc-2.2.5-32!

The problem "does not" exist in glibc-2.2.5-30
Comment 3 Jakub Jelinek 2002-04-18 11:43:46 EDT
Sorry, typo. Wanted to say fixed in 2.2.5-33+ (currently 2.2.5-34).

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