==12351== Memcheck, a memory error detector ==12351== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==12351== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==12351== Command: ./test_functions ==12351== Parent PID: 4329 ==12351== --12351-- --12351-- Valgrind options: --12351-- -v --12351-- --tool=memcheck --12351-- --leak-check=yes --12351-- --track-origins=yes --12351-- --log-file=valout --12351-- Contents of /proc/version: --12351-- Linux version 4.13.0-37-generic (buildd@lcy01-amd64-012) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)) #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 --12351-- --12351-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-rdtscp-sse3-avx --12351-- Page sizes: currently 4096, max supported 4096 --12351-- Valgrind library directory: /usr/lib/valgrind --12351-- Reading syms from /bin/bash --12351-- Considering /bin/bash .. --12351-- .. CRC mismatch (computed c27dcca5 wanted 5aa3c568) --12351-- object doesn't have a symbol table --12351-- Reading syms from /lib/x86_64-linux-gnu/ld-2.23.so --12351-- Considering /lib/x86_64-linux-gnu/ld-2.23.so .. --12351-- .. CRC mismatch (computed aa979a42 wanted 9019bbb7) --12351-- Considering /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so .. --12351-- .. CRC is valid --12351-- Reading syms from /usr/lib/valgrind/memcheck-amd64-linux --12351-- Considering /usr/lib/valgrind/memcheck-amd64-linux .. --12351-- .. CRC mismatch (computed eea41ea9 wanted 2009db78) --12351-- object doesn't have a symbol table --12351-- object doesn't have a dynamic symbol table --12351-- Scheduler: using generic scheduler lock implementation. --12351-- Reading suppressions file: /usr/lib/valgrind/default.supp ==12351== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12351-by-ale3andros-on-??? ==12351== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12351-by-ale3andros-on-??? ==12351== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12351-by-ale3andros-on-??? ==12351== ==12351== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12351== don't want to do, unless you know exactly what you're doing, ==12351== or are doing some strange experiment): ==12351== /usr/lib/valgrind/../../bin/vgdb --pid=12351 ...command... ==12351== ==12351== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12351== /path/to/gdb ./test_functions ==12351== and then give GDB the following command ==12351== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12351 ==12351== --pid is optional if only one valgrind process is running ==12351== --12351-- REDIR: 0x401cfd0 (ld-linux-x86-64.so.2:strlen) redirected to 0x3809e181 (???) --12351-- Reading syms from /usr/lib/valgrind/vgpreload_core-amd64-linux.so --12351-- Considering /usr/lib/valgrind/vgpreload_core-amd64-linux.so .. --12351-- .. CRC mismatch (computed 2567ccf6 wanted 49420590) --12351-- object doesn't have a symbol table --12351-- Reading syms from /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so --12351-- Considering /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so .. --12351-- .. CRC mismatch (computed 0e27c9a8 wanted ac585421) --12351-- object doesn't have a symbol table ==12351== WARNING: new redirection conflicts with existing -- ignoring it --12351-- old: 0x0401cfd0 (strlen ) R-> (0000.0) 0x3809e181 ??? --12351-- new: 0x0401cfd0 (strlen ) R-> (2007.0) 0x04c31020 strlen --12351-- REDIR: 0x401b920 (ld-linux-x86-64.so.2:index) redirected to 0x4c30bc0 (index) --12351-- REDIR: 0x401bb40 (ld-linux-x86-64.so.2:strcmp) redirected to 0x4c320d0 (strcmp) --12351-- REDIR: 0x401dd30 (ld-linux-x86-64.so.2:mempcpy) redirected to 0x4c35270 (mempcpy) --12351-- Reading syms from /lib/x86_64-linux-gnu/libtinfo.so.5.9 --12351-- object doesn't have a symbol table --12351-- Reading syms from /lib/x86_64-linux-gnu/libdl-2.23.so --12351-- Considering /lib/x86_64-linux-gnu/libdl-2.23.so .. --12351-- .. CRC mismatch (computed 39227170 wanted ab6e2c22) --12351-- Considering /usr/lib/debug/lib/x86_64-linux-gnu/libdl-2.23.so .. --12351-- .. CRC is valid --12351-- Reading syms from /lib/x86_64-linux-gnu/libc-2.23.so --12351-- Considering /lib/x86_64-linux-gnu/libc-2.23.so .. --12351-- .. CRC mismatch (computed 7a8ee3e4 wanted a5190ac4) --12351-- Considering /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.23.so .. --12351-- .. CRC is valid --12351-- REDIR: 0x52f6a00 (libc.so.6:strcasecmp) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x52f2280 (libc.so.6:strcspn) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x52f8cf0 (libc.so.6:strncasecmp) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x52f46f0 (libc.so.6:strpbrk) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x52f4a80 (libc.so.6:strspn) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x52f614b (libc.so.6:memcpy@GLIBC_2.2.5) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x52f4400 (libc.so.6:rindex) redirected to 0x4c308a0 (rindex) --12351-- REDIR: 0x52f0d10 (libc.so.6:__GI_strcmp) redirected to 0x4c31fe0 (__GI_strcmp) --12351-- REDIR: 0x52f2720 (libc.so.6:strlen) redirected to 0x4c30f60 (strlen) --12351-- REDIR: 0x52f2b70 (libc.so.6:__GI_strncmp) redirected to 0x4c31710 (__GI_strncmp) --12351-- REDIR: 0x52f0ab0 (libc.so.6:__GI_strchr) redirected to 0x4c30a00 (__GI_strchr) --12351-- REDIR: 0x52f5860 (libc.so.6:memchr) redirected to 0x4c32170 (memchr) --12351-- REDIR: 0x52fd760 (libc.so.6:strchrnul) redirected to 0x4c34da0 (strchrnul) --12351-- REDIR: 0x52f63b0 (libc.so.6:__GI_mempcpy) redirected to 0x4c34fa0 (__GI_mempcpy) --12351-- REDIR: 0x52fb470 (libc.so.6:__GI_memcpy) redirected to 0x4c32b00 (__GI_memcpy) --12351-- REDIR: 0x52f61b0 (libc.so.6:memset) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x52f6240 (libc.so.6:__GI_memset) redirected to 0x4c344c0 (memset) --12351-- REDIR: 0x52f6890 (libc.so.6:__GI_stpcpy) redirected to 0x4c33f80 (__GI_stpcpy) --12351-- REDIR: 0x52f2160 (libc.so.6:strcpy) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x530c9d0 (libc.so.6:__strcpy_sse2_unaligned) redirected to 0x4c31040 (strcpy) --12351-- REDIR: 0x52f2b20 (libc.so.6:strncmp) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x53aca90 (libc.so.6:__strncmp_sse42) redirected to 0x4c317f0 (__strncmp_sse42) --12351-- REDIR: 0x52f0cd0 (libc.so.6:strcmp) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x5306570 (libc.so.6:__strcmp_sse2_unaligned) redirected to 0x4c31f90 (strcmp) --12351-- REDIR: 0x52f28c0 (libc.so.6:strnlen) redirected to 0x4c30ee0 (strnlen) --12351-- REDIR: 0x537d480 (libc.so.6:__strcpy_chk) redirected to 0x4c34e10 (__strcpy_chk) --12351-- REDIR: 0x52f0a80 (libc.so.6:index) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x52fb3f0 (libc.so.6:memcpy@@GLIBC_2.14) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x5306820 (libc.so.6:__memcpy_sse2_unaligned) redirected to 0x4c324a0 (memcpy@@GLIBC_2.14) --12351-- REDIR: 0x52f43c0 (libc.so.6:strncpy) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x530d000 (libc.so.6:__strncpy_sse2_unaligned) redirected to 0x4c31570 (__strncpy_sse2_unaligned) ==12353== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12353-by-ale3andros-on-??? ==12353== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12353-by-ale3andros-on-??? ==12353== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12353-by-ale3andros-on-??? ==12353== ==12353== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12353== don't want to do, unless you know exactly what you're doing, ==12353== or are doing some strange experiment): ==12353== /usr/lib/valgrind/../../bin/vgdb --pid=12353 ...command... ==12353== ==12353== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12353== /path/to/gdb ./test_functions ==12353== and then give GDB the following command ==12353== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12353 ==12353== --pid is optional if only one valgrind process is running ==12353== ==12353== ==12353== HEAP SUMMARY: ==12353== in use at exit: 0 bytes in 0 blocks ==12353== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==12353== ==12353== All heap blocks were freed -- no leaks are possible ==12353== ==12353== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12353== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12352== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12352-by-ale3andros-on-??? ==12352== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12352-by-ale3andros-on-??? ==12352== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12352-by-ale3andros-on-??? ==12352== ==12352== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12352== don't want to do, unless you know exactly what you're doing, ==12352== or are doing some strange experiment): ==12352== /usr/lib/valgrind/../../bin/vgdb --pid=12352 ...command... ==12352== ==12352== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12352== /path/to/gdb ./test_functions ==12352== and then give GDB the following command ==12352== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12352 ==12352== --pid is optional if only one valgrind process is running ==12352== ==12352== ==12352== HEAP SUMMARY: ==12352== in use at exit: 0 bytes in 0 blocks ==12352== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==12352== ==12352== All heap blocks were freed -- no leaks are possible ==12352== ==12352== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12352== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12354== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12354-by-ale3andros-on-??? ==12354== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12354-by-ale3andros-on-??? ==12354== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12354-by-ale3andros-on-??? ==12354== ==12354== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12354== don't want to do, unless you know exactly what you're doing, ==12354== or are doing some strange experiment): ==12354== /usr/lib/valgrind/../../bin/vgdb --pid=12354 ...command... ==12354== ==12354== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12354== /path/to/gdb ./test_functions ==12354== and then give GDB the following command ==12354== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12354 ==12354== --pid is optional if only one valgrind process is running ==12354== ==12354== ==12354== HEAP SUMMARY: ==12354== in use at exit: 0 bytes in 0 blocks ==12354== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==12354== ==12354== All heap blocks were freed -- no leaks are possible ==12354== ==12354== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12354== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12356== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12356-by-ale3andros-on-??? ==12356== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12356-by-ale3andros-on-??? ==12356== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12356-by-ale3andros-on-??? ==12356== ==12356== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12356== don't want to do, unless you know exactly what you're doing, ==12356== or are doing some strange experiment): ==12356== /usr/lib/valgrind/../../bin/vgdb --pid=12356 ...command... ==12356== ==12356== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12356== /path/to/gdb ./test_functions ==12356== and then give GDB the following command ==12356== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12356 ==12356== --pid is optional if only one valgrind process is running ==12356== ==12357== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12357-by-ale3andros-on-??? ==12357== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12357-by-ale3andros-on-??? ==12357== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12357-by-ale3andros-on-??? ==12357== ==12357== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12357== don't want to do, unless you know exactly what you're doing, ==12357== or are doing some strange experiment): ==12357== /usr/lib/valgrind/../../bin/vgdb --pid=12357 ...command... ==12357== ==12357== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12357== /path/to/gdb ./test_functions ==12357== and then give GDB the following command ==12357== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12357 ==12357== --pid is optional if only one valgrind process is running ==12357== ==12357== ==12357== HEAP SUMMARY: ==12357== in use at exit: 0 bytes in 0 blocks ==12357== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==12357== ==12357== All heap blocks were freed -- no leaks are possible ==12357== ==12357== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12357== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12356== ==12356== HEAP SUMMARY: ==12356== in use at exit: 0 bytes in 0 blocks ==12356== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==12356== ==12356== All heap blocks were freed -- no leaks are possible ==12356== ==12356== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12356== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12360== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12360-by-ale3andros-on-??? ==12360== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12360-by-ale3andros-on-??? ==12360== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12360-by-ale3andros-on-??? ==12360== ==12360== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12360== don't want to do, unless you know exactly what you're doing, ==12360== or are doing some strange experiment): ==12360== /usr/lib/valgrind/../../bin/vgdb --pid=12360 ...command... ==12360== ==12360== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12360== /path/to/gdb ./test_functions ==12360== and then give GDB the following command ==12360== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12360 ==12360== --pid is optional if only one valgrind process is running ==12360== ==12361== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12361-by-ale3andros-on-??? ==12361== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12361-by-ale3andros-on-??? ==12361== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12361-by-ale3andros-on-??? ==12361== ==12361== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12361== don't want to do, unless you know exactly what you're doing, ==12361== or are doing some strange experiment): ==12361== /usr/lib/valgrind/../../bin/vgdb --pid=12361 ...command... ==12361== ==12361== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12361== /path/to/gdb ./test_functions ==12361== and then give GDB the following command ==12361== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12361 ==12361== --pid is optional if only one valgrind process is running ==12361== ==12359== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12359-by-ale3andros-on-??? ==12359== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12359-by-ale3andros-on-??? ==12359== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12359-by-ale3andros-on-??? ==12359== ==12359== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12359== don't want to do, unless you know exactly what you're doing, ==12359== or are doing some strange experiment): ==12359== /usr/lib/valgrind/../../bin/vgdb --pid=12359 ...command... ==12359== ==12359== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12359== /path/to/gdb ./test_functions ==12359== and then give GDB the following command ==12359== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12359 ==12359== --pid is optional if only one valgrind process is running ==12359== ==12359== ==12359== HEAP SUMMARY: ==12359== in use at exit: 0 bytes in 0 blocks ==12359== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==12359== ==12359== All heap blocks were freed -- no leaks are possible ==12359== ==12359== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12359== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12362== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12362-by-ale3andros-on-??? ==12362== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12362-by-ale3andros-on-??? ==12362== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12362-by-ale3andros-on-??? ==12362== ==12362== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12362== don't want to do, unless you know exactly what you're doing, ==12362== or are doing some strange experiment): ==12362== /usr/lib/valgrind/../../bin/vgdb --pid=12362 ...command... ==12362== ==12362== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12362== /path/to/gdb ./test_functions ==12362== and then give GDB the following command ==12362== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12362 ==12362== --pid is optional if only one valgrind process is running ==12362== ==12362== ==12362== HEAP SUMMARY: ==12362== in use at exit: 0 bytes in 0 blocks ==12362== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==12362== ==12362== All heap blocks were freed -- no leaks are possible ==12362== ==12362== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12362== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) --12351-- REDIR: 0x52f6850 (libc.so.6:stpcpy) redirected to 0x4a286f0 (_vgnU_ifunc_wrapper) --12351-- REDIR: 0x530dfe0 (libc.so.6:__stpcpy_sse2_unaligned) redirected to 0x4c34120 (__stpcpy_sse2_unaligned) ==12364== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12364-by-ale3andros-on-??? ==12364== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12364-by-ale3andros-on-??? ==12364== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12364-by-ale3andros-on-??? ==12364== ==12364== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12364== don't want to do, unless you know exactly what you're doing, ==12364== or are doing some strange experiment): ==12364== /usr/lib/valgrind/../../bin/vgdb --pid=12364 ...command... ==12364== ==12364== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12364== /path/to/gdb ./test_functions ==12364== and then give GDB the following command ==12364== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12364 ==12364== --pid is optional if only one valgrind process is running ==12364== ==12363== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12363-by-ale3andros-on-??? ==12363== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12363-by-ale3andros-on-??? ==12363== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12363-by-ale3andros-on-??? ==12363== ==12363== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12363== don't want to do, unless you know exactly what you're doing, ==12363== or are doing some strange experiment): ==12363== /usr/lib/valgrind/../../bin/vgdb --pid=12363 ...command... ==12363== ==12363== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12363== /path/to/gdb ./test_functions ==12363== and then give GDB the following command ==12363== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12363 ==12363== --pid is optional if only one valgrind process is running ==12363== ==12365== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-12365-by-ale3andros-on-??? ==12365== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-12365-by-ale3andros-on-??? ==12365== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-12365-by-ale3andros-on-??? ==12365== ==12365== TO CONTROL THIS PROCESS USING vgdb (which you probably ==12365== don't want to do, unless you know exactly what you're doing, ==12365== or are doing some strange experiment): ==12365== /usr/lib/valgrind/../../bin/vgdb --pid=12365 ...command... ==12365== ==12365== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==12365== /path/to/gdb ./test_functions ==12365== and then give GDB the following command ==12365== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=12365 ==12365== --pid is optional if only one valgrind process is running ==12365== ==12363== ==12363== HEAP SUMMARY: ==12363== in use at exit: 0 bytes in 0 blocks ==12363== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==12363== ==12363== All heap blocks were freed -- no leaks are possible ==12363== ==12363== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==12363== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)