This is the mail archive of the
libc-alpha@cygnus.com
mailing list for the glibc project.
libc-2.0.7 compiled programs segfault with 2.0.102 in _IO_old_file_close_it
- To: libc-alpha@cygnus.com
- Subject: libc-2.0.7 compiled programs segfault with 2.0.102 in _IO_old_file_close_it
- From: pp@netppl.fi
- Date: Fri, 20 Nov 1998 22:25:27 GMT
>Submitter-Id: net
>Originator: Pekka Pietikäinen
>Organization:
>Confidential: no
>Synopsis: libc-2.0.7 compiled programs segfault with 2.0.102 in _IO_old_file_close_it
>Severity: serious
>Priority: medium
>Category: libc
>Class: sw-bug
>Release: libc-2.0.102
>Environment:
Host type: i386-redhat-linux-gnu
System: Linux connecting.netppl.fi 2.1.128 #4 Sat Nov 14 01:58:50 EET 1998 i686 unknown
Architecture: i686
Addons: crypt glibc-compat linuxthreads
Build CC: egcs
Compiler version: egcs-2.92.17 19981026 (gcc2 ss-980609 experimental)
Kernel headers: 2.1.128
Symbol versioning: yes
Build static: yes
Build shared: yes
Build pic-default: no
Build profile: yes
Build omitfp: no
Build bounded: no
Build static-nss: no
Stdio: libio
>Description:
Some glibc-2.0.7 compiled programs (like Red Hat timeconfig and
Window Maker) segfault under 2.0.102:
Program received signal SIGSEGV, Segmentation fault.
0x400db201 in _IO_old_file_close_it (fp=0x804fe50) at oldfileops.c:140
oldfileops.c:140: No such file or directory.
JDK 1.1.7a also segfaults, but diagnosing whether the problem is
the same is quite difficult because of the use of threads and source not
being available.
>How-To-Repeat:
Run the programs causing problems
>Fix:
Recompiling the programs under 2.0.102 fixes the problem,
but obviously there's a problem in the compatibility code in 102.