You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by st...@apache.org on 2010/11/22 02:58:11 UTC
svn commit: r1037588 -
/subversion/branches/performance/subversion/libsvn_fs_util/caching.c
Author: stefan2
Date: Mon Nov 22 01:58:11 2010
New Revision: 1037588
URL: http://svn.apache.org/viewvc?rev=1037588&view=rev
Log:
If we have to bail out due to some file handle cache creation error,
we should pass a proper error message to the handler.
* subversion/libsvn_fs_util/caching.c
(svn_fs__get_global_file_handle_cache): pass err message to handler
Modified:
subversion/branches/performance/subversion/libsvn_fs_util/caching.c
Modified: subversion/branches/performance/subversion/libsvn_fs_util/caching.c
URL: http://svn.apache.org/viewvc/subversion/branches/performance/subversion/libsvn_fs_util/caching.c?rev=1037588&r1=1037587&r2=1037588&view=diff
==============================================================================
--- subversion/branches/performance/subversion/libsvn_fs_util/caching.c (original)
+++ subversion/branches/performance/subversion/libsvn_fs_util/caching.c Mon Nov 22 01:58:11 2010
@@ -110,13 +110,19 @@ svn_fs__get_global_file_handle_cache(voi
svn_pool_create(NULL));
if (err)
{
+ char buffer[1024];
+ const char *message = svn_err_best_message(err,
+ buffer,
+ sizeof(buffer));
+
svn_error_clear(err);
/* We need the file handle cache. The only way that an error could
* occur would be some threading error. In that case, there is no
* way we could continue - not even in some limp home mode.
*/
- SVN_ERR_MALFUNCTION_NO_RETURN();
+ svn_error__malfunction(FALSE, __FILE__, __LINE__, message);
+ abort();
}
}