OK, I figured out what the problem was.
Very important (as it turns out) piece of information that I forgot:
I copied the svn executable from subversion/clients/cmdline/svn to the top
of my working copy of Subversion and *used that copy*. When I use the
original subversion/clients/cmdline/svn then everything behaves as expected
(no segment faults).
So in response to your question below, yes I did change something :-)
However, now the issue becomes: A copy of the svn executable cannot run 'svn
status' and behaves strangely for other commands. Should this be regarded as
a bug? Or just user error for not linking to the original executable (or
using make install)?
>From: Philip Martin <firstname.lastname@example.org>
>"Mason Thomas" <email@example.com> writes:
>Are you sure you didn't change something, or run some other command?
Actually, I copied the svn executable.
>What does your repository look like? What about your working copy?
>Do you have local modifications? It's not clear to me whether your
>working copy is for the Subversion repository or your own repository.
> > 'svn help' works still.
> > 'svn update' successfully updated to r3946 (success is measured by
>So your working copy is the Subversion tree?
> > using an older version of Subversion: svn status -u).
>I assume you have multiple Subversion installations, try
>$ ldd /path/to/svn
>and see whether it is linked to the correct Subversion/APR libraries.
> > However, during
> > the update, it just spits out a bunch of lines of "Update complete"
> > instead of printing the filenames affected. At the end of the update,
> > svn prints "Fetching external item into .".
>That's what you get when the directory has an 'svn:external' property,
>so your working copy is not the Subversion tree? Try running the
>command 'svn pg svn:external' to see the property value.
> > Probably this is not enough info to track down the problem, but please
> > give me some pointers and I will attempt to help track it down.
>If the core dump is repeatable then do
>$ gdb /path/to/svn
I tried running gdb on my svn copy, but it complains that it is an unknown
Ahhh...now I notice that svn is actually a shell script?! How do I debug
this with gdb??
>(gdb) run status -u (or whatever arguments you give to the svn command)
>Program received SIGSEGV
>(gdb) bt full
>which will print out a stack trace.
The new MSN 8: smart spam protection and 2 months FREE*
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Dec 1 21:58:30 2002