[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: rpm 4.1-1.06 segfaulting after glibc upgrade




I also got the strace (strace rpm -Uvvh --nodeps glibc-devel-2.3.2-11.9.i386.rpm):

____________________________________________________________________
................................................................................
...............................................................................
open("/lib/libc.so.6", O_RDONLY)        = 7
read(7, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0008U\1\000"..., 1024) = 1024
fstat64(7, {st_mode=S_IFREG|0755, st_size=18872134, ...}) = 0
old_mmap(NULL, 1198788, PROT_READ|PROT_EXEC, MAP_PRIVATE, 7, 0) = 0x40515000
mprotect(0x40634000, 23236, PROT_NONE)  = 0
old_mmap(0x40634000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 7, 0x11e000) = 0x40634000
old_mmap(0x40638000, 6852, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40638000
close(7)                                = 0
open("/lib/ld-linux.so.2", O_RDONLY)    = 7
read(7, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0@\n\0\000"..., 1024) = 1024
fstat64(7, {st_mode=S_IFREG|0755, st_size=622108, ...}) = 0
old_mmap(NULL, 75828, PROT_READ|PROT_EXEC, MAP_PRIVATE, 7, 0) = 0x403f4000
mprotect(0x40406000, 2100, PROT_NONE)   = 0
old_mmap(0x40406000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 7, 0x11000) = 0x40406000
close(7)                                = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
_________________________________________________________________________

Please help us out.

Thanks,
Manu Garg





I am sorry if this is already listed somewhere. I tried to search on google, but couldn't find the clue.

We have a x86 box running redhat 8.0. We decided to upgrade glibc 3.2.2 as some packages don't get compiled with glibc 2.2.95. We downloaded the src rpm (glibc-2.3.2-11.9.src.rpm) and compiled it on our machine using rpmbuild. RPM building went on fine.


We first upgraded glibc-common and then glibc. That was it and rpm started giving segmentation fault for all rpms just after that. All other programs seem to run fine except rpm. Following is the output from rpm:

___________________________________________________________________________________________________


D: ============== glibc-profile-2.3.2-11.9.i386.rpm

D: Expected size:     23224620 = lead(96)+sigs(180)+pad(4)+data(23224340)

D:   Actual size:     23224620

D: glibc-profile-2.3.2-11.9.i386.rpm: MD5 digest: OK (c19f22aef43403950dccdd195abac6f9)

D: opening  db environment /var/lib/rpm/Packages joinenv

D: opening  db index       /var/lib/rpm/Packages rdonly mode=0x0

D: locked   db index       /var/lib/rpm/Packages

D: opening  db index       /var/lib/rpm/Providename rdonly mode=0x0

D: opening  db index       /var/lib/rpm/Pubkeys rdonly mode=0x0

D:  read h#     919 Header sanity check: OK

D: ========== DSA pubkey id 219180cddb42a60e

D:  read h#     612 Header V3 DSA signature: OK, key ID db42a60e

D:      added binary package [0]

D: found 0 source and 1 binary packages

D: ========== +++ glibc-profile-2.3.2-11.9

D: opening  db index       /var/lib/rpm/Depends create mode=0x0

D:  Requires: rpmlib(PayloadFilesHavePrefix) <= 4.0-1       YES (rpmlib provides)

D:  Requires: rpmlib(CompressedFileNames) <= 3.0.4-1        YES (rpmlib provides)

D: ========== --- glibc-profile-2.2.93-5

D: opening  db index       /var/lib/rpm/Requirename rdonly mode=0x0

D: closed   db index       /var/lib/rpm/Depends

D: ========== recording tsort relations

D: ========== tsorting packages (order, #predecessors, #succesors, tree, depth)

D:     0    0    0    1    0 -glibc-profile-2.2.93-5

D: ========== successors only (presentation order)

D:     1    0    0    0    0 +glibc-profile-2.3.2-11.9

D: installing binary packages

D: closed   db index       /var/lib/rpm/Pubkeys

D: closed   db index       /var/lib/rpm/Providename

D: closed   db index       /var/lib/rpm/Requirename

D: closed   db index       /var/lib/rpm/Packages

D: closed   db environment /var/lib/rpm/Packages

D: opening  db environment /var/lib/rpm/Packages joinenv

D: opening  db index       /var/lib/rpm/Packages create mode=0x42

D: getting list of mounted filesystems

D: sanity checking 2 elments

D: opening  db index       /var/lib/rpm/Name create mode=0x42

D:  read h#     612 Header V3 DSA signature: OK, key ID db42a60e

D: computing 24 file fingerprints

Preparing...                D: computing file dispositions

D: opening  db index       /var/lib/rpm/Basenames create mode=0x42

########################################### [100%]

D: ========== +++ glibc-profile-2.3.2-11.9

D: Expected size:     23224620 = lead(96)+sigs(180)+pad(4)+data(23224340)

D:   Actual size:     23224620

D:   install: glibc-profile-2.3.2-11.9 has 12 files, test = 0

Segmentation fault

____________________________________________________________________________________


As other programs are not showing problems, this problem seems to be specific to rpm. Please help me out!!


Manu Garg,

Tata Consultancy Services

ForwardSourceID:NT000017B2    
DISCLAIMER: The information contained in this message is intended only and solely for the addressed individual or entity indicated in this message and for the exclusive use of the said addressed individual or entity indicated in this message (or responsible for delivery
of the message to such person) and may contain legally privileged and confidential information belonging to Tata Consultancy Services. It must not be printed, read, copied, disclosed, forwarded, distributed or used (in whatsoever manner) by any person other than the addressee. 
Unauthorized use, disclosure or copying is strictly prohibited and may constitute unlawful act and can possibly attract legal action, civil and/or criminal. The contents of this message need not necessarily reflect or endorse the views of Tata Consultancy Services on any subject matter.
Any action taken or omitted to be taken based on this message is entirely at your risk and neither the originator of this message nor Tata Consultancy Services takes any responsibility or liability towards the same. Opinions, conclusions and any other information contained in this message 
that do not relate to the official business of Tata Consultancy Services shall be understood as neither given nor endorsed by Tata Consultancy Services or any affiliate of Tata Consultancy Services. If you have received this message in error, you should destroy this message and may please notify the sender by e-mail. Thank you.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]