[vox-tech] Segmentation Fault with RPM --rebuilddb

[Richard Crawford]

I believe I've narrowed the problem down to some ugly Ximian packages
that are on my system (I love Evolution, but I am seriously questioning
my wisdom in putting the entire Ximian GNOME desktop onto my computer).

I communicated with a fellow at Ximian who suggests downgrading all of
my Ximian packages, being especially careful with glibc, and doing a
package-by-package upgrade of the RPM's on my system.

Grumble.

I wonder if it would be easier to zark my Linux installation as it is,
tarring up my home directory into my data partition, and reinstalling
RH8.0 from scratch?

Opinions?  Suggestions?  Advice?  Offers to come and do it for me
(newbie fear setting in -- I can handle most kernel panics and just
about everything else that comes up on my system pretty much on my own
now, thanks to the extraordinary patience of my brother-in-law and this
awesome LUG, but OS installs always intimidate the bejeebers out of me,
even when I'm just doing a Windows install)?

Richard


On Thu, 2003-01-02 at 13:53, Richard Crawford wrote:
> On Thu, 2003-01-02 at 11:58, ME wrote:
> 
> > Fail after a pwrite? Hmm. Would you mind running this again, but instead try:
> > # strace -f rpm --rebuilddb
> > ? The -f also does the strace on child processes spawned by the first. I
> > am betting that "rpm --rebuilddb" actually calls a different program that
> > is segfaulting and the strace is not contintuing to the next app being
> > called.
> > (Just guessing)
> > 
> > If the output of the lines just preceeding the SIGSEGV is the same, you
> > dont need to paste it in again, just let us know. If the output leading up
> > to the Segfault is different, could you include the new run/output like
> > you did this time? :-)
> 
> I ran,
> 
> 	# strace -f rpm --rebuilddb
> 
> and got exactly the same output.  Eerie.
> 
> I should point out that other functions of rpm (-i, -e, -qa, etc.)
> function normally.  It's when I run it with --rebuilddb that it bombs.
> 
> 
> > On the topic of "time". After you run the program, does it immediately
> > return the message "segfault" or does it take a while and occur after lots
> > of disk activity?
> 
> It's immediate.  There's no hard drive activity at all.
-- 
Slainte,
Richard S. Crawford

mailto:rscrawford@mossroot.com		http://www.mossroot.com
AIM:  Buffalo2K   ICQ: 11646404  Yahoo!: rscrawford
MSN:  underpope@hotmail.com

"It is only with the heart that we see rightly; what is essential is
invisible to the eye."  --Antoine de Saint Exupery

vi vi vi - the editor of the beast