Run it in a terminal and see what kind of errors it gives you. If that doesn't work compile it with fewer optimization flags and with the '-g' option for debug, then attach 'gdb' to it or load it in 'gdb'. i.e.
# now within the gdb shell, it should say '(gdb)', type
the program should start, then use the program normally and when it crashes, gdb will tell you what went wrong (you may not understand what it's saying, but if you post it here or to the maintainers of the program, someone might).