Re: Error 139 and svn core dump (solved)

[Garret Wilson <ga...@globalmentor.com>]

Ben Collins-Sussman wrote:
> It sounds like you either have libc problems, or that (somehow) your svn
> binary linked against older libsvn_* libraries in your system.  Is that
> possible?  Look at 'ldd' output.  Purge your system of old libraries.

Thank you, everyone, for your input on my seemingly endless stream of 
problems. I never want to go through this again.

After I tried to recompile and reinstall glibc (which I had successfully 
done before), I was told I couldn't because I had an old gcc. Yep, my 
gcc was 2.96. I downloaded, compiled, and installed gcc 3.3.2, and svn 
worked! I'm now happily running 0.35.1 on client and server.

Questions still linger in my mind:

* What's the relationship between gcc and glibc?
* Why did gcc work before for the other svn versions?
* Why does 
http://www.python.org/cgi-bin/moinmoin/Python20FrequentlyAskedQuestions 
seem to indicate that gcc will be updated by updating glibc?
* Why did my updating glibc, which fixed the problem for compiling 
Python 2 on Red Hat 7, cause problems with gcc?

I can only assume that updating glibc via RPM to fix the Python problem 
somehow *reverted* my gcc to an old version that was buggy and created a 
buggy svn. (I don't know why Python compiled correctly, though. I guess 
I should go back and recompile it just in case.)

Garret



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org