【发布时间】:2021-01-07 20:18:19
【问题描述】:
我正在尝试创建一个函数,将 2 个字符串(str1 和 str2)连接成一个由 char 分隔符分隔的新字符串(str3)。不幸的是,我的这个函数发生了内存泄漏,我真的不知道为什么,因为我最后释放了 str3。
示例:str_join_string("ABC","DEF",'|') ---> "ABC|DEF"
代码如下:
char *str_join_string(const char *str1, const char *str2, char separator) {
char *str3;
size_t len = str_length(str1)+ str_length(str2)+1;
size_t i = 0;
size_t j = 0;
str3 = (char * )calloc(len, sizeof(char));
if(str3 == NULL){
printf("Impossible d'allouer la mémoire");
return NULL;
}
while(str1[i] != '\0' && str1 != NULL){
str3[i] = str1[i];
i++;
}
str3[i] = separator;
i+=1;
while(str2[j] != '\0' && str2 != NULL){
str3[i+j] = str2[j];
j++;
}
str3[len] = '\0';
return str3;
}
我要补充一点,我不能使用 strcat() 之类的任何函数或来自 string.h 的任何函数。
Valgrind 展示的内容:
==4300== Searching for pointers to 3 not-freed blocks
==4300== Checked 131,560 bytes
==4300==
==4300== 4 bytes in 1 blocks are definitely lost in loss record 1 of 3
==4300== at 0x4C31B25: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4300== by 0x13E3B2: str_join_string (stringslib.c:238)
==4300== by 0x13E545: str_join_array (stringslib.c:283)
==4300== by 0x137065: JoinArrayTest_OneEmpty_Test::TestBody() (stringslib_test.cc:779)
==4300== by 0x1652A9: HandleSehExceptionsInMethodIfSupported<testing::Test, void> (gtest.cc:2611)
==4300== by 0x1652A9: void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2647)
==4300== by 0x15A9DE: testing::Test::Run() [clone .part.658] (gtest.cc:2686)
==4300== by 0x15AC61: Run (gtest.cc:2677)
==4300== by 0x15AC61: testing::TestInfo::Run() [clone .part.659] (gtest.cc:2863)
==4300== by 0x15B350: Run (gtest.cc:2837)
==4300== by 0x15B350: testing::TestSuite::Run() [clone .part.660] (gtest.cc:3017)
==4300== by 0x15BAF4: Run (gtest.cc:2997)
==4300== by 0x15BAF4: testing::internal::UnitTestImpl::RunAllTests() (gtest.cc:5709)
==4300== by 0x165769: HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool> (gtest.cc:2611)
==4300== by 0x165769: bool testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) (gtest.cc:2647)
==4300== by 0x15AD82: testing::UnitTest::Run() (gtest.cc:5292)
==4300== by 0x11C08E: RUN_ALL_TESTS (gtest.h:2485)
==4300== by 0x11C08E: main (stringslib_test.cc:799)
==4300==
我希望你能帮助我,因为我现在真的很迷茫。
--------编辑------ 是的,我完全忘了添加调用者,这是我释放内存的地方:
TEST(JoinStringTest, Simple) {
char *buf = str_join_string("ABC", "XYZ", '|');
ASSERT_TRUE(buf != NULL);
EXPECT_EQ(buf[0], 'A');
EXPECT_EQ(buf[1], 'B');
EXPECT_EQ(buf[2], 'C');
EXPECT_EQ(buf[3], '|');
EXPECT_EQ(buf[4], 'X');
EXPECT_EQ(buf[5], 'Y');
EXPECT_EQ(buf[6], 'Z');
EXPECT_EQ(buf[7], '\0');
free(buf);
}
【问题讨论】:
-
当一个函数返回时,它已经执行完毕。您的
free(str3)行将永远不会被调用,并且是“死代码”。str_join_stringcannot freestr3不管怎样,因为它会将它返回给调用者; 调用者必须负责在不再需要返回值时释放它。 -
确实,我只是忘记将调用者添加到我使用 free() 的帖子中,我将删除这些代码行。对不起。
-
什么是
str_length()?它与标准库的strlen()有何不同? -
@JohnBollinger str_length() 返回与 strlen() 相同的结果,但是对于这个任务,禁止使用 strlen() 我必须自己制作一个。
-
你确定你已经展示了 Valgrind 将泄漏归因于的测试吗? Valgrind 的堆栈跟踪中的
JoinArrayTest_OneEmpty_Test::TestBody()似乎与TEST(JoinStringTest, Simple)不匹配。
标签: c memory-leaks string-concatenation c-strings function-definition