메모리릭이 없다면 valgrind의 오류를 무시해도 괞찮나요?

Question

valgrind로 메모릭을 체크하는 데 계속 이상한 오류들이 나옵니다. 프로그램의 실행이나 메모리 릭 문제도 없는데, 계속 잘못된 메모리를 참조한다고 알립니다.주로 str같은 무자열 함수나 배열,구조체에서 많이 나오는 데 원인이 뭔가요? 그냥 무시해도 되나요?다른 프로젝트에서도 비슷한게 나왔는데 무시해도 문제가 없었습니다.&#61;&#61;28737&#61;&#61; Syscall param stat(file_name) points to unaddressable byte(s) &#61;&#61;28737&#61;&#61; at 0x4C436DA: _xstat (xstat.c:35) &#61;&#61;28737&#61;&#61; by 0x109C60: file_path_check (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x109D8E: process_sync_file (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x10960E: main (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; Address 0x1ffeffcdf0 is on thread 1's stack &#61;&#61;28737&#61;&#61; 8008 bytes below stack pointer &#61;&#61;28737&#61;&#61; &#61;&#61;28737&#61;&#61; Invalid read of size 1 &#61;&#61;28737&#61;&#61; at 0x483EF46: strlen (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) &#61;&#61;28737&#61;&#61; by 0x10A4A6: add_path (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x109DA6: process_sync_file (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x10960E: main (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; Address 0x1ffeffcdf0 is on thread 1's stack &#61;&#61;28737&#61;&#61; 7768 bytes below stack pointer &#61;&#61;28737&#61;&#61; &#61;&#61;28737&#61;&#61; Invalid read of size 1 &#61;&#61;28737&#61;&#61; at 0x483EF54: strlen (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) &#61;&#61;28737&#61;&#61; by 0x10A4A6: add_path (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x109DA6: process_sync_file (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x10960E: main (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; Address 0x1ffeffcdf1 is on thread 1's stack &#61;&#61;28737&#61;&#61; 7767 bytes below stack pointer &#61;&#61;28737&#61;&#61; &#61;&#61;28737&#61;&#61; Invalid read of size 1 &#61;&#61;28737&#61;&#61; at 0x10A511: add_path (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x109DA6: process_sync_file (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x10960E: main (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; Address 0x1ffeffcdf0 is on thread 1's stack &#61;&#61;28737&#61;&#61; 7776 bytes below stack pointer &#61;&#61;28737&#61;&#61; &#61;&#61;28737&#61;&#61; Invalid read of size 1 &#61;&#61;28737&#61;&#61; at 0x10A522: add_path (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x109DA6: process_sync_file (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x10960E: main (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; Address 0x1ffeffcdf1 is on thread 1's stack &#61;&#61;28737&#61;&#61; 7775 bytes below stack pointer &#61;&#61;28737&#61;&#61; &#61;&#61;28737&#61;&#61; Invalid read of size 1 &#61;&#61;28737&#61;&#61; at 0x10A538: add_path (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x109DA6: process_sync_file (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x10960E: main (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; Address 0x1ffeffcdf2 is on thread 1's stack &#61;&#61;28737&#61;&#61; 7774 bytes below stack pointer &#61;&#61;28737&#61;&#61; &#61;&#61;28737&#61;&#61; Invalid read of size 1 &#61;&#61;28737&#61;&#61; at 0x10A54E: add_path (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x109DA6: process_sync_file (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x10960E: main (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; Address 0x1ffeffcdf3 is on thread 1's stack &#61;&#61;28737&#61;&#61; 7773 bytes below stack pointer &#61;&#61;28737&#61;&#61; &#61;&#61;28737&#61;&#61; Invalid read of size 1 &#61;&#61;28737&#61;&#61; at 0x10A56A: add_path (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x109DA6: process_sync_file (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; by 0x10960E: main (in /home/nesusa/file_sync_program/bin/server) &#61;&#61;28737&#61;&#61; Address 0x1ffeffcdf4 is on thread 1's stack &#61;&#61;28737&#61;&#61; 7772 bytes below stack pointer &#61;&#61;28737&#61;&#61;

mirheeoj · Answer

소스를 보여주셔야 확인이 될 것 같은데요.static code analysis가 false positives 상황을 낼 수 있는 건 사실인데, 검증은 해봐야죠. 코드를 보고 "최소한 우리 프로그램이 동작하는 조건에선 이건 절대 일어나지 않을 일이다" 라는 확신이 있을때에만 무시 처리를 하셔야 하고, 평소 프로그램 동작에 문제없다고 그냥 넘어가면 안 됩니다.문자열, 배열, 구조체에서 많이 나오는건 제가 보기엔 자연스럽습니다. 메모리 관련 구현 실수나 보안 문제 등이 대개 저런 걸 다룰 때 나오니까 말이지요.

네스사 · Answer

void add_path(file_list_t **file_list, char *path) { if (NULL == path) { printf("add_path의 매개변수가 올바르지 않습니다.
"); return; } file_list_t *current_file_data = NULL; HASH_FIND_STR(*file_list, path, current_file_data); if (NULL != current_file_data) { printf("%s는 이미 존재하는 경로입니다.
", path); return; } struct stat file_data; memset(&file_data, 0, sizeof(file_data)); stat(path, &file_data); SHA256_CTX sha256; SHA256_Init(&sha256); current_file_data = (file_list_t *)malloc(sizeof *current_file_data); current_file_data->path = strndup(path, MAX_LENGTH); current_file_data->file_path_size = strlen(path) + 1; current_file_data->update_time = file_data.st_mtime; current_file_data->file_data_size = file_data.st_size; current_file_data->state = 0; check_sum_generater(path, current_file_data->check_sum, &sha256); HASH_ADD_KEYPTR(hh, *file_list, current_file_data->path, strlen(path), current_file_data); printf("%s가 추가되었습니다.
", path); }코드 입니다. uthash로 해쉬 테이블에 요소를 추가하는 함수입니다

메모리릭이 없다면 valgrind의 오류를 무시해도 괞찮나요?

2개의 답변

Q&A 목록