The general description of a
segmentation fault is described here.
While looking online is usually a good way to get started, you may not always have the exact issue. You can check how much memory is physcially installed in the computer, run your program in the background (when starting the program in a command-line interface, postfix or add at the end the & sign) and then type in top and hit enter. You will then see the memory usage for the device and how much memory each program is using.
The other part of your message means that the system state (core) was 'dumped' to an output file that you can go through and see exactly what happened at the failure point. They're usually difficult to read, however it's good practice for general administration to look through one and try to find your messages (search for the name of the program that failed, errors, etc...)
The logfiles in the system in /var/log/ might help as well - depending on your distribution there is usually one specific one that's mainly logged to, but the name might change between syslog/authlog/messages/etc... I think RHEL is /var/log/messages, but I can't remember.
A final option would be to use a different type of software than CAP3 that does the same thing and see if that fails as well.
Go forth and debug! Oh, and feel free to post again if you get stuck or find any interesting messages.