所以基本上我的输入是一个未知大小的字符串。 我所做的是创建一个函数来扫描它并为每个字符动态分配内存。动态字符串内存泄漏
char* GetUnknownStr(){
char* string = NULL;
char input = 0;
int charCount = 0;
//scan for chars until ENTER is pressed
while (input != '\n'){
scanf("%c", &input);
//on last iteration (when ENTER is pressed) break from loop
if (input == '\n')
break;
//realloc new amount of chars
string = (char*)realloc(string, (++charCount)*sizeof(char));
//check if realloc didnt fail
if (string == NULL){
puts("failed to allocate");
return 0;
}
//assign char scanned into string
string[charCount-1] = input;
}
//realloc 1 more char for '\0' in the end of string
string = (char*)realloc(string, (++charCount)*sizeof(char)); <--leak
string[charCount-1] = '\0';
return string;
}
的valgrind:
==30911== HEAP SUMMARY:
==30911== in use at exit: 4 bytes in 1 blocks
==30911== total heap usage: 7 allocs, 6 frees, 16 bytes allocated
==30911==
==30911== 4 bytes in 1 blocks are definitely lost in loss record 1 of 1
==30911== at 0x4A05255: realloc (vg_replace_malloc.c:476)
==30911== by 0x40091F: GetUnknownStr (in /u/stud/krukfel/C/e5/a.out)
==30911== by 0x40266B: main (in /u/stud/krukfel/C/e5/a.out)
==30911==
==30911== LEAK SUMMARY:
==30911== definitely lost: 4 bytes in 1 blocks
==30911== indirectly lost: 0 bytes in 0 blocks
==30911== possibly lost: 0 bytes in 0 blocks
==30911== still reachable: 0 bytes in 0 blocks
==30911== suppressed: 0 bytes in 0 blocks
==30911==
==30911== For counts of detected and suppressed errors, rerun with: -v
==30911== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 6 from 6)
由于某种原因,即时得到了内存泄漏,不能找出原因,使用Valgrind的尝试,但不可能从它什么太大的意义。 谢谢!
Valgrind告诉你什么? –
你怎么知道你第一次有泄漏? – Devolus