C
carl
I have made an application that throws a segmentation fault when I run it.
../MyApp
Segmentation fault
I have then tried to run it with Valgrind:
valgrind --leak-check=yes --track-origins=yes ./MyApp
==8389==
==8389== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 8 from 1)
==8389== malloc/free: in use at exit: 0 bytes in 0 blocks.
==8389== malloc/free: 13,153,309 allocs, 13,153,309 frees,
8,529,290,300 bytes allocated.
==8389== For counts of detected errors, rerun with: -v
==8389== All heap blocks were freed -- no leaks are possible.
So Valgrind cannot find any errors but I still get a segmentation fault when
running the app without Valgrind.
I have used almost a week to go through the code and I have written
unit-test for each part. Any ideas on how to find this error when valgrind
fails to find it or is the just a program that is cursed?
../MyApp
Segmentation fault
I have then tried to run it with Valgrind:
valgrind --leak-check=yes --track-origins=yes ./MyApp
==8389==
==8389== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 8 from 1)
==8389== malloc/free: in use at exit: 0 bytes in 0 blocks.
==8389== malloc/free: 13,153,309 allocs, 13,153,309 frees,
8,529,290,300 bytes allocated.
==8389== For counts of detected errors, rerun with: -v
==8389== All heap blocks were freed -- no leaks are possible.
So Valgrind cannot find any errors but I still get a segmentation fault when
running the app without Valgrind.
I have used almost a week to go through the code and I have written
unit-test for each part. Any ideas on how to find this error when valgrind
fails to find it or is the just a program that is cursed?