summaryrefslogtreecommitdiff
path: root/tests-clar/repo/setters.c
diff options
context:
space:
mode:
authornulltoken <emeric.fermas@gmail.com>2012-04-23 11:07:19 +0200
committernulltoken <emeric.fermas@gmail.com>2012-04-23 11:07:19 +0200
commitbaf861a511a2c5cb091fcaa510c1b66331c49bed (patch)
treef681e5d2b8ab898b53ce76610cbbc6c684e821e0 /tests-clar/repo/setters.c
parentc1aefb35dd39efa0045a9925520b4715f82433e3 (diff)
downloadlibgit2-baf861a511a2c5cb091fcaa510c1b66331c49bed.tar.gz
Fix git_repository_set_odb() refcount issue
git_repository_free() calls git_odb_free() if the owned odb is not null. According to the doc, when setting a new odb through git_repository_set_odb() the caller has to take care of releasing the odb by himself.
Diffstat (limited to 'tests-clar/repo/setters.c')
-rw-r--r--tests-clar/repo/setters.c21
1 files changed, 21 insertions, 0 deletions
diff --git a/tests-clar/repo/setters.c b/tests-clar/repo/setters.c
index 0c3b28d33..6242d8541 100644
--- a/tests-clar/repo/setters.c
+++ b/tests-clar/repo/setters.c
@@ -57,3 +57,24 @@ void test_repo_setters__setting_a_new_index_on_a_repo_which_has_already_loaded_o
*/
repo = NULL;
}
+
+void test_repo_setters__setting_a_new_odb_on_a_repo_which_already_loaded_one_properly_honors_the_refcount(void)
+{
+ git_odb *new_odb;
+
+ cl_git_pass(git_odb_open(&new_odb, "./testrepo.git/objects"));
+ cl_assert(((git_refcount *)new_odb)->refcount == 1);
+
+ git_repository_set_odb(repo, new_odb);
+ cl_assert(((git_refcount *)new_odb)->refcount == 2);
+
+ git_repository_free(repo);
+ cl_assert(((git_refcount *)new_odb)->refcount == 1);
+
+ git_odb_free(new_odb);
+
+ /*
+ * Ensure the cleanup method won't try to free the repo as it's already been taken care of
+ */
+ repo = NULL;
+}