Please attach log files as text/* MIME type (maybe by renaming them to
*.txt) so it's easier to read/reply to them.
Now, the first thing that jumps out is that some of the actual
parameters are 0x or 0x1000; for example:
#14 0x13f639fd8 in serve(conn=(svn_ra_svn_conn_st *) 0x
Shot in the dark, but: does the crash reproduce in non-threaded modes?
(such as -X/--foreground, or alternatively -i if you have netcat or
inetd to test it with)
Mark Raymond wrote on Thu, Nov 01, 2012 at 21:21:21 -:
> Background:
>
> A week or so ago, I tried to set up svnserve with sasl aut
Hi,
On Fri, Nov 02, 2012 at 08:35:11PM +0200, Daniel Shahaf wrote:
> Please attach log files as text/* MIME type (maybe by renaming them to
> *.txt) so it's easier to read/reply to them.
>
> Now, the first thing that jumps out is that some of the actual
> parameters are 0x or 0x1000;
Andreas Mohr wrote on Fri, Nov 02, 2012 at 19:44:24 +0100:
> Hi,
>
> On Fri, Nov 02, 2012 at 08:35:11PM +0200, Daniel Shahaf wrote:
> > Please attach log files as text/* MIME type (maybe by renaming them to
> > *.txt) so it's easier to read/reply to them.
> >
> > Now, the first thing that jumps o
I recently upgraded Subversion edge to 3.2.0-3352.100 which gave me Subversion
1.7.7.
Since then every now and then when I commit I get the following error:
Commit
Commit failed (details follow):
Server sent unexpected return value (500 Internal Server Error) in response to
POST request for '/s
Bob Archer writes:
> I recently upgraded Subversion edge to 3.2.0-3352.100 which gave me
> Subversion 1.7.7.
>
> Since then every now and then when I commit I get the following error:
>
> Commit
> Commit failed (details follow):
> Server sent unexpected return value (500 Internal Server Error) i
Greetings,
We are trying to track down a couple of problems we are having here at my
company using SVN.
We have been using SVN quite happily for years, but starting a couple of weeks
ago we started getting a number of errors.
Problem #1 generates errors on the client that look like this:
REPO
> Now, the first thing that jumps out is that some of the actual parameters
are 0x or 0x1000; for example:
> #14 0x13f639fd8 in serve(conn=(svn_ra_svn_conn_st *) 0x,
params=(serve_params_t *) 0x, pool=(apr_pool_t *) 0x) at
> which might suggest a stack smash, or
Ralph Lacy writes:
> Problem #1 generates errors on the client that look like this:
>
> REPORT of '/svn/!svn/vcc/default': Chunk delimiter was invalid (http://code)
>
> On the server side, it looks like this:
>
> [Fri Nov 02 12:01:10 2012] [error] [client 172.31.99.13] Error writing base64
> dat
