Question : catching cores

Saeven · 06-13-2002, 02:11 PM

Hello,

I have this big project I am working on, and sometimes a missed quotation or a %s that gets fed an int causes a segmentation fault you know how it is. I used to code for a mud that had cores dumped each time the program hosed itself, and I could navigate the cores with gdb. If I could catch cores it would save me alot of time.

I'm no linux guru, and I was wondering if anyone could give me some help, a primer even, on how to catch cores. Before you ask, when I check ulimit it says unlimited

Cheers!
Saeven

Mara · 06-13-2002, 03:36 PM

Working on cores isn't the best idea I know. It's much better to include special code (for development versions) to write every program stem to a log file. Then you can easily find out what was wrong. That's a method I use...

Saeven · 06-13-2002, 04:29 PM

It's rather big - I have last function log prints in all major parts, but there are about 1500 methods to the program in over 100000 lines of code. It would be quite a spammy log since it's a real-time system. Cores are a must - anyone know how to get them going?

Cheers,
Alex