>So I got around to downloading the GDB file
Once you get gdb, have you decided what you are going to do with it? Do you have debug info in your application?
In most cases, unless you have a development machine, you just record the fact you have a core file and use file(1) to see what signal and executable. Then you remove it. If you start seeing more of them, then you do something.
"chatr cmmload" will give you a start of the list of shlibs.
You can also copy the core file and executable and ALL of the shlibs it uses to a supported machine and then use gdb there.
>all these P95270.812 files are located in the "/disk3/cmmData" directory. They are files from another PC that get uploaded to the directory and a cron job starts the C program
Is that program cmmload?
Perhaps there are too many files in cmmData to handle. Why not move half of them aside and see if it works. If they are removed after being processed, then move the other half back.
