Segmentation fault on svn status

[Mason Thomas <ml...@hotmail.com>]

Running svn status causes a segmentation fault.

Version: svn r3929
Compiled evening of Nov. 27 with apr and apr-utils cvs versions that were 
current as of that time.
neon 0.23.5
bdb 4.0.14
Running on Debian Linux

The first time I ran 'svn status' and also 'svn status -u' Subversion 
behaved as expected.
Maybe related, maybe not: Then I ran 'svn version' and get 'Unknown 
command'. But after this, svn status gives segmentation faults.
'svn help' works still.
'svn update' successfully updated to r3946 (success is measured by using an 
older version of Subversion: svn status -u). 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 .".

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.

-Mason



_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. 
http://join.msn.com/?page=features/virus


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

Re: Segmentation fault on svn status

[Philip Martin <ph...@codematters.co.uk>]

"Mason Thomas" <ml...@hotmail.com> writes:

> The first time I ran 'svn status' and also 'svn status -u' Subversion
> behaved as expected.
> 
> Maybe related, maybe not: Then I ran 'svn version' and get 'Unknown
> command'. But after this, svn status gives segmentation faults.

It is extremely unlikely that running 'svn version' caused the
problem.

Lets see if I understand: you ran 'svn status -u' and it worked, you
ran 'svn version' and got 'unknown command' (the expected output) and
now any further attempts to run 'svn status -u' cause a core dump, all
with the same working copy.

Are you sure you didn't change something, or run some other command?
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
(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.

-- 
Philip Martin

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