RE: svnserve crash

2012-11-02 Thread Mark Raymond
> 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

Re: svnserve crash

2012-11-02 Thread Daniel Shahaf
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

Re: svnserve crash

2012-11-02 Thread Andreas Mohr
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;

Re: svnserve crash

2012-11-02 Thread Daniel Shahaf
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

Re: svnserve crash

2012-11-02 Thread Daniel Shahaf
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