On Tue, Jan 27, 2015 at 10:38:31AM -0500, Lathan Bidwell wrote: > I am running SVN 1.6 (will be upgrading to 1.8.8) through apache 2.4 / > mod_perl. > > I'm trying to get email notifications of errors, but whenever libsvn fails > one of its assertions, it dies, and causes the whole apache process to core > dump / seg fault. > > Is there some way to either check for these assertions in a non-lethal way > before hand, or make it possible to surivve the error so my error reporting > can run? > > Usually these assertions are problems with my url handling: double slash, > or slash at end of directory. But I'd still like those errors to be > reported, so I know that my users are hitting problems. > > Thanks, > Lathan
A failure in svn_uri_is_canonical() sounds like you are running something (a Perl script since you mention mod_perl?) against the SVN APIs that provides bad input to SVN. Is this the case? If so, whatever is running will need to be fixed to provide valid input. To find out what SVN considers canonical please refer to the comment on top of this file: https://svn.apache.org/repos/asf/subversion/trunk/subversion/include/svn_dirent_uri.h as well as the comment on top of the function svn_uri_canonicalize() in the same file. 1.6 is very old so it's possible that your problems will disappear after an update to 1.8. If that's not the case then please invest some time into writing a problem report that includes detailed information about your setup (actual error messages extracted from log files, config files, hook scripts you are running, etc.)
