On Tue, Aug 11, 2009 at 12:43 PM, Allie K<alliekbean@gmail.com> wrote:
This problem is driving me crazy, and I'm not quite sure what's wrong with the server. I'm running Bahamut 1.8.6 with ircservices 5.1.19. At random times, the ircd seems to just segfault, dumping core. I'm not really a [..] only has a handful of users on it (maybe 5 at the most?) so it isn't under heavy load or anything. I'm running the server on 64-bit Ubuntu 9.04 under a Xen virtual machine (commercial VPS host). I didn't see a place to check
When you get a corefile, one of the easiest ways to take a look at it is to have GDB (the GNU debugger) installed then issue #gdb -c /path/to/corefile /path/to/program eg # gdb -c core.23589 /usr/local/bin/ircd You will get a (gdb) prompt, now you can ask gdb to give you a backtrace: (gdb) bt full If that's too many hundreds of pages long just "backtrace" Use (gdb) quit when done to exit gdb. The output from a full backtrace may help identify the problem. If you take a look at the output (and in particular the bottom and top of the stack), or post it... Note that it works best if you have provided "-ggdb" as a CFLAG, and you do not compile with any strip options. The output may also be hard to decipher if you compiled with heavy optimizations beyond the simple -O option, e.g. if the GCC options you used to compile the program contained -O2, -O3 Or one of those hundreds of elaborate -f* optimization options such as "-fomit-frame-pointer -funroll-loops -finline-functions" Your debugger may not be able to provide all that much information. So if 'bt' from within gdb doesn't provide much, you may want to tweak the CFLAGs settings -- -J