Bug 700 - RealAudio 5.0 (rvplayer) crashes with glibc-2.0.108
RealAudio 5.0 (rvplayer) crashes with glibc-2.0.108
Status: CLOSED WONTFIX
Product: Red Hat Raw Hide
Classification: Retired
Component: glibc (Show other bugs)
1.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Cristian Gafton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-01-06 01:58 EST by jehamby
Modified: 2011-05-10 22:26 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-02-16 11:18:00 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)

  None (edit)
Description jehamby 1999-01-06 01:58:41 EST
rvplayer crashes with a segmentation fault under RedHat.
Here's one workaround which may prove helpful for running
other Linux binaries which crash under glibc 2.0.108 and for
which source is not available:

* Copy these files from glibc-2.0.7 into /cpt:

ld-2.0.7.so         libc.so.6           libm-2.0.7.so
libresolv.so.2
ld-linux.so.2       libdl-2.0.7.so      libm.so.6
libc-2.0.7.so       libdl.so.2          libresolv-2.0.7.so

* Rename rvplayer to rvplayer.bin and make this shell script
named rvplayer:

#!/bin/sh
LD_LIBRARY_PATH=/cpt:/usr/lib/Real
export LD_LIBRARY_PATH
/usr/bin/rvplayer.bin $*

* Edit rvplayer.bin (with, e.g. emacs) and change the
reference to /lib/ld-linux.so.2 into /cpt/ld-linux.so.2

If you have a better workaround, or ideally, can fix the
compatibility code in glibc-2.0.108, please let me know.
Comment 1 Bill Nottingham 1999-01-06 10:39:59 EST
FYI, it won't work without patching with most of the sound drivers in
2.2 anyways...
Comment 2 jehamby 1999-01-06 13:37:59 EST
Yup, that's why I've been using ALSA (http://alsa.jcu.cz/).
Comment 3 Cristian Gafton 1999-02-16 11:18:59 EST
This is a problem witb the changes in the 2.2 kernel audio drivers,
and Real will have to fix their code.

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