http://qa.mandrakesoft.com/show_bug.cgi?id=4468
Product: libgnome-vfs0
Component: libgnome-vfs0
Summary: largefile danger (miscompiled libraries?)
Product: libgnome-vfs0
Version: 1.0.5-9mdk
Platform: PC
URL: http://ac-archive.sf.net/largefile
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libgnome-vfs0
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The largefile-problem detector-script has found
these instances of possibly miscompiled libraries:
/usr/lib/libaviplay-0.7.so.0 DANGER lseek../lseek64 lseek../lseek64
/usr/lib/libaviplay-0.7.so.0.0.38 DANGER lseek../lseek64
/usr/lib/libgnomevfs.so.0 DANGER fopen../fopen64
/usr/lib/libgnomevfs.so.0.0.0 DANGER fopen../fopen64
/usr/lib/libkadm5srv.so.5 DANGER fopen../fopen64
/usr/lib/libkadm5srv.so.5.1 DANGER fopen../fopen64
As you see, these libraries import both 32bit and 64bit off_t
variants of the open/seek symbols for either 64bit-largefile
or 32bit-long files in the system. Very very few libraries
are even smarter than the detector-script using explicit
imports via _LARGEFILE64_SOURCE but it does not look like to
be the case for these.
To test yourself, download the detector-script off_t_problem.pl
from my site, it has become a quite sophisticated tool over time.
To see the same result, run it as
perl off_t_problem.pl /usr/lib/lib*.so.*
and you may want to try also
perl off_t_problem.pl /usr/lib/gnome-vfs-2.0/modules/*
while the latter 32bit-off_t modules might be okay simply
as we may expect that the imported libraries are not called
on files with a filesize beyond 2GB.
Further information can be found at the largefile-page at
http://ac-archive.sf.net/largefile with crossreferences to
the relevant standards, the freshmeat and lsb discussions.
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
