Those files are coredumps.
Roughly put, they're a snapshot of the process (the numbers tell the process id) leading up to a crash. They're mainly used to track down bugs, and are loaded into tools such as gdb. Once loaded, you could use commands such as bt (backtrace), which will show the chain of functioncalls which led to the crash.
google for core dump and/or gdb, and you'll find alot more information.
nml375 wrote:Those files are coredumps.
Roughly put, they're a snapshot of the process (the numbers tell the process id) leading up to a crash. They're mainly used to track down bugs, and are loaded into tools such as gdb. Once loaded, you could use commands such as bt (backtrace), which will show the chain of functioncalls which led to the crash.
google for core dump and/or gdb, and you'll find alot more information.
Will do.
I assume gdb is something that I would need to ask the server admin to install?
If it's not already been installed, you'd probably be better off having your admin install it, though you could try and build it yourself.
A third, though more complicated way, would be to build it locally - though for this you'll need a copy of the binary (eggdrop + modules) and any dynamic library it has loaded on the local server. Personally, I try to avoid this option whenever possible.
Also see the doc/BUG-REPORT in your eggdrop istallation for details on what you can do with the output from the coredumps.