axellee1994
commented
4 months ago @gysiang Okay noted on this. What command was used to trigger this issue?
Closed gysiang closed 4 months ago
axellee1994
commented
4 months ago @gysiang Okay noted on this. What command was used to trigger this issue?
==7809== in use at exit: 208,494 bytes in 230 blocks ==7809== total heap usage: 567 allocs, 337 frees, 235,376 bytes allocated ==7809== ==7809== 187 bytes in 1 blocks are definitely lost in loss record 26 of 68 ==7809== at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==7809== by 0x112406: ft_strdup (in /home/gyong-si/Documents/42/minishell/minishell) ==7809== by 0x10DF78: get_path (pipex_utils_3.c:86) ==7809== by 0x10D867: get_command_path (execute_utils_1.c:42) ==7809== by 0x10D92A: exec_cmd (execute_utils_1.c:84) ==7809== by 0x10D113: execute_single_command (execute_3.c:42) ==7809== by 0x10E69A: pipex (pipex.c:115) ==7809== by 0x10987A: process_command_line (main.c:50) ==7809== by 0x10987A: main_loop (main.c:75) ==7809== by 0x1094FB: main (main.c:87)