Hotboot Snippet and Core File

Posted by Diablo on Fri 08 Jul 2005 03:34 PM — 6 posts, 25,435 views.

#0
Well.. I recently installed Greven's Hotboot Snippet for SWR onto my SWR MUD. It took a bit of re-reading to get it to work, but now when I hotboot and someone quits, the MUD crashes. I need some help locating the problem, although I believe its not extracting the character.

Also, I do not get CORE files with a crash. I would like some help with this also.

Thanx.

-Diablo
USA #1
Read over Nick's gdb guide for how to enable core dumps. After it hotboots, attach gdb to the process and crash the MUD.
#2
Ok, I did the whole gdb thing and I managed to fix a few bugs I had problems with on my MUD. Now for the Hotboot problem.

This is what I typed,

cd swd/area
gdb ../src/swreality.exe
run 8632
(then the loading stuff came up)
On the MUD I typed, hotboot, and this is what I got.

Fri Jul 8 05:41:03 2005 :: Hotboot initiated by Diablo.
Fri Jul 8 05:41:03 2005 :: Preserving world state....
Fri Jul 8 05:41:03 2005 :: IMC: Shutting down network.
Fri Jul 8 05:41:03 2005 :: Saving player files and connection states....
Fri Jul 8 05:41:03 2005 :: Executing hotboot....

Program received signal SIGTRAP, Trace/breakpoint trap.
0x400007a0 in _start () from /lib/ld-linux.so.2

I've never seen something like that before, I hope someone can help me with it.

-Diablo
Amended on Fri 08 Jul 2005 07:49 PM by Diablo
USA #3
Well try attaching it after the hotboot, since hotboot "swaps" exec files and sometimes does not work with gdb.
#4
When it does that, type continue and it will continue with it onto the newly booted copy of your MUD. I had a problem similar on my SWR MUD with that copyover. I found that changing some of the descriptor stuff worked, because my copy of SWR had different things to init the descriptor than the copyover's.
Canada #5
Since it is hotbooting ok, but is crashing afterwards, it may be changes that you have made to the system, likely the space system. Check to make sure that the space code uses the same methods for str_dup and STRALLOC that your using, I've come across this before when installing it in a few code bases, as the other coders changes names to use str_dup instead of STRALLOC I think, so there were conflictions. Actually, since its when the character quits, check the character code portion for the same.