A classic multithread program to learn how to avoid data racing and dead lock issues
Here is a few pre-setup possibilities. Note that all of them are adding the args_to_test variable as an argument to run ./philo
make go:: Let's Go mode- For checking how the threads are running, without changes.
make gdb:: GNU DeBugger mode- For debugging propuses, with a lot of pre-setup executables, like
run, breakpoint atmain, andset args.
- For debugging propuses, with a lot of pre-setup executables, like
make val:: Valgrind mode- For checking memory leaks, this will calls valgridn with a lot of options.
make hel:: Helgrind mode- For checking Threads errors, this will calls valgrind with the
helgrindtool activated.
- For checking Threads errors, this will calls valgrind with the
make drd:: Data Race Detector - DRD mode- For checking Data Race errors from Threads, this will calls valgrind with the
drdtool activated.
- For checking Data Race errors from Threads, this will calls valgrind with the
make sani_t:: Fsanitize for Threads mode- For checking various forms of undefined or suspicious behaviors, switching to
threadsmode.
- For checking various forms of undefined or suspicious behaviors, switching to
make sani_a:: Fsanitize for Address mode- For checking various forms of undefined or suspicious behaviors, switching to
addressmode.
- For checking various forms of undefined or suspicious behaviors, switching to
