This video explains how to debug a crash using gdb and valgrind. You can run gdb without a breakpoint (as gdb will automatically stop when the process crashes), and analyze values of variables at the point of crash (using print, backtrace, and frame commands).
Running valgrind will let you know what memory errors are occuring, which most likely are the cause of the crash.
Note: For giving arguments to executable inside gdb, you can user a command like below
(gdb) run arg1 arg2...
Note: I apologise for the audio quality issues. Setup fixes are in progress....