[NBLUG/talk] RPM Segmentation Fault

Todd Cary todd at aristesoftware.com
Sun Dec 7 07:49:00 PST 2003


Mark -

In addition to the kernel update, the automatic up2date has a very long 
list of packages that it wants to update.  The list [see another post] 
includes

 glibc-2.3.2-101.1.i386.rpm      
 glibc-2.3.2-101.1.i686.rpm      
 glibc-common-2.3.2-101.1.i386..>
 glibc-debug-2.3.2-101.1.i386.rpm
 glibc-devel-2.3.2-101.1.i386.rpm
 glibc-headers-2.3.2-101.1.i38..>
 glibc-profile-2.3.2-101.1.i38..>
 glibc-utils-2.3.2-101.1.i386.rpm
 grep-2.5.1-17.2.i386.rpm        

There are two glibc-2.3.2-101.1 packages: one i386 and one i686.  The 
updated kernel is i686.  This brings up some questions for me (I hope 
these questions are helpful to others too):

1) What is the difference between an i386 and i686 package?

2) The kernel at boot up is listed as i686.  What is a i386 and i686 kernel?

3) Do I need to update all of those packages?

Trying to get a handle on Linux/Fedora

Todd
Mark Street wrote:

>Hmmm, my experience stated below is with a fedora box with all updates 
>installed using yum.  I have since installed and erased both Firebird and 
>Interbase at least twice since your initial post without a hiccup....  And by 
>the way I built the php rpm in such a way that an UPdate if and when it 
>becomes available will NOT overwrite my custom package, but it will download 
>the src rpm for me and get it ready for a custom build.  Then all I have to 
>do is tweak the .spec file, build it and install it.  consistency...... 
>custom
>
>It's hard to give you any advice with the information you provide and the 
>inability to reproduce said behavior on my fedora box.
>
>Is it rpm that is seg faulting on the install?
>
>Try cleaning up the rpm database, rebuild it and try again after your up2date. 
>(I have never used up2date.... ; ) , but hey..)  I really don't think this is 
>all worth another install of fedora though.  I think you are wasting your 
>time doing all these installs.  I prefer a sniper to a shotgun.
>
>To rebuild the rpm database....
># rpm --rebuilddb
>
>Then try to install Firebird....
>
>I don't know what to tell you, I have never known or seen rpm seg fault.....  
>I have seen it hang and do other strange behaviors from time to time... but 
>never seg fault.
>
>You might try using the strace command with your rpm install of firebird to 
>see where it is bombing.
>
>strace rpm -ivh Firebird-blah...rpm   you will get a ton of shit but it may 
>hand you a clue.
>
>Anyone else have any ideas on where to find clues to this strangeness.  Maybe 
>a bad RAM module?
>
>On Saturday 06 December 2003 20:10, Todd Cary wrote:
>  
>
>>Mark Street wrote:
>>    
>>
>>>corrupted package?
>>>
>>># rpm -e InterBaseSS_LI
>>>Saved a copy of isc4.gdb in /tmp
>>># rpm -ivh FirebirdSS-1.5.0.4027-RC7.i686.rpm
>>>Preparing...                ###########################################
>>>[100%] 1:FirebirdSS            
>>>########################################### [100%] starting Firebird
>>>server: service [  OK  ]
>>>Running gsec to modify SYSDBA password
>>>rGSEC> GSEC>
>>>Running ed to modify /etc/init.d/firebird
>>>1495
>>>1494
>>>
>>>On Friday 05 December 2003 08:09, Todd Cary wrote:
>>>      
>>>
>>>>I am trying to install a FirebirdSS rpm on my "learning box".  The one I
>>>>have on my online Linux server and the latest I downloaded both give me
>>>>a "Segmentation Error".  This is my first encounter with this error and
>>>>Google did not yield anything that helped me understand what is going on
>>>>and how to get around it.
>>>>
>>>>Help...
>>>>        
>>>>
>>Here is what I found:
>>
>>I reinstalled Fedora again and did the up2date updates.  Same problem:
>>Segmeentation Fault when I tried to use the FirebirdSS rpm.
>>
>>Tried rebooting with the "before up2date" version: same problem
>>
>>Reinstalled Fedora *and* did *not* do the up2date updates: FirebirdSS
>>installs fine!
>>
>>I do not have enough knowledge about Linux and the myiad of pieces that
>>are in play here, but it appears that something is updated that
>>interfers with rpm.  The version of rpm before and after the updates was
>>the same.
>>
>>Any help would be GREATLY appreciated......
>>
>>Todd
>>    
>>
>
>  
>

-- 




More information about the talk mailing list