Bug 30751

Summary: rpm 4.0 core dump
Product: [Retired] Red Hat Linux Reporter: Kiri Wagstaff <wkiri>
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED WORKSFORME QA Contact: David Lawrence <dkl>
Severity: high Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-03-06 05:48:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kiri Wagstaff 2001-03-06 03:34:00 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (X11; U; Linux 2.2.17-21mdk i686)


I installed rpm 4.0 from the source rpm.  I then upgraded from glibc 2.1.3
to glibc 2.2.2.  Now I get a core dump from rpm (didn't get this core dump
before upgrading glibc, but I'm not sure what's causing it). 



Reproducible: Always
Steps to Reproduce:
1. Install rpm 4.0.
2. Install glibc 2.2.2. 
3. Try to upgrade or install any .rpm.
	

Actual Results:  
[root@astra src]# rpm -U tix-8.3.2-7mdk.i586.rpm
rpm: ../iconv/skeleton.c:304: gconv: Assertion `outbufstart == ((void *)0)'
failed.
Aborted (core dumped)



Expected Results:  Ideally, a successful upgrade (or a message about
required dependencies).
Comment 1 Kiri Wagstaff 2001-03-06 03:35:47 UTC 
Note that glibc 2.2.2 does update several entries in /usr/lib/gconv, if that's
what's going on here.
Comment 2 Kiri Wagstaff 2001-03-06 04:12:13 UTC 
Modification: rpm 4.0 came from the tar.gz, not the source rpm.
Comment 3 Kiri Wagstaff 2001-03-06 05:48:24 UTC 
Ok, I was able to eliminate the core dump by recompiling and reinstalling rpm
4.0.  I had to add the following two lines to popt.c to get it to compile this
time:

#define FLT_MAX 1e+37
#define FLT_MIN 1e-37

As far as I can tell, one possible clash between rpm 4 and glibc2.2.2 is that
they both write very different versions of /usr/local/include/libintl.h.  There
may be (probably are) others.
Comment 4 Jeff Johnson 2001-03-06 13:57:43 UTC 
There's an i18n structure incompatibility between glibc-2.1.3 and glibc-2.2.2
that affects statically linked binaries like /bin/rpm. You'll need to recompile
rpm
with glibc-2.2.2.