On 2004-12-16 10:09-0600, Ben Collins-Sussman wrote:
> >The intresting thing is that the Apache was segfaulting
> I have no idea why apache would segfault, though. Can you look more
> into that?
Not very much, sorry.
> I mean, we have no python tests that call 'svn lock', so I'd like to
> know what you're seeing, or how to reproduce.
The server OS is Linux/amd64.
In general I am running plain test framework against locking branch,
but it seems that you could trigger the same thing with just import or commit.
(with client from locking branch or from trunk, doesn't matter)
It seems that you could read (ls, co) but not write (commit/import)
anything to the repository, if that is any help.
[10:27:40] $ ./inst/svn_locking/bin/svn import -m ' ' \
<some dir> http://127.0.0.1:42024/test
svn: applying log message to
/test/!svn/wbl/f87034f9-5eeb-0310-b9dd-f55ca1238f8f/0: Could not read
status line: connection was closed by server. (http://127.0.0.1:42024)
$ tail -n 3 inst/httpd-2.0.x/logs/error_log
[Thu Dec 16 10:26:21 2004] [notice] Apache/2.0.53-dev (Unix) DAV/2 SVN/1.2.0-dev configured -- resuming normal operations
[Thu Dec 16 10:27:51 2004] [notice] child pid 29767 exit signal Segmentation fault (11)
[Thu Dec 16 10:27:52 2004] [notice] child pid 29807 exit signal Segmentation fault (11)
I have rebuild everything and this still happens, so it is something
in the locking branch or in my system. However, svn/trunk, and
svn/1.1.x are both working with the very same setup. Could you
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Dec 16 18:53:40 2004