Just make sure you compiled all the source with -ggdb switch so that the executable has full symbol tables.
It makes the executables larger, but it keeps enough information for a more useful debugging session.
If you run your zones/world stripped of symbol information, you can go recompile (assuming you've not made changes) with -ggdb and then use gdb on your new zone/world with that core. GDB will probably complain as follows, but should take it just fine:
Code:
warning: exec file is newer than core file.
BTW, in general it drops core.pid for multithreaded applications (where pid is the process ID of the thread that cored) and just plain "core" for single threaded apps.
You can also see what application generated the core file, if you don't have gdb installed for some reason (not that the core file will do you much good, at least on that system):
Code:
% strings core.10415| head
tdH$
CORE
CORE
zone
./zone qeynos 192.168.0.5 7101 192.168.0.5
CORE
zone
-panel
CORE
CORE
Threaded Mode
