Re: Subversion 0.14.0 problems/bugs (memory fault with -m & svn update)

Jason White <jasonjgw@pacific.net.au> writes:

> I found the following bug: if a relatively long log message is specified as a single
> command line argument, between single quotes under the Bourne shell,
> svn produces a memory fault.

Exact error message help when trying to diagnose problems, then we
don't have to guess :-)

Are you getting a SEGV running the client, a SEGV running the server,
an "out of memory" message, or what?

>
> Example:
> svn ci filename -m 'This is a very long and detailed log message which
> would probably trigger a memory fault under svn 0.14.0, and possibly
> later versions.'

Let's assume you get a SEGV running the client.

I cannot reproduce this with HEAD, and it runs clean under valgrind.
You will need to do more to identify the problem. Please run the
program under gdb and show us the stack trace

$ gdb /path/to/svn
(gdb) r ci filename -m 'the long message....'
Program received SIGSEGV
(gdb) bt

> However, when I now run svn update
> [subversion@jdc]$ svn update
>
> apr_error: #20014, src_err 0 : <Error string not specified yet>
> REPORT request failed on /repos/svn/trunk
>
> apr_error: #20014, src_err 0 : <Error string not specified yet>
> The REPORT status was 400, but expected 200.

This indicates that you are using a proxy that doesn't support all the
HTTP methods required. Reconfigure your proxy (if you can), or use
port 81, see

http://subversion.tigris.org/project_faq.html#proxy

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