Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
auth_update crash
Dec 23, 2017, 10:15 pm
By Remcon
check_tumble
Dec 18, 2017, 7:21 pm
By Remcon
parse description bug
Dec 15, 2017, 10:08 pm
By Remcon
Couple bugs
Dec 12, 2017, 5:42 pm
By Remcon
Bug in disarm( )
Nov 12, 2017, 6:54 pm
By GatewaySysop
LoP 1.46
Author: Remcon
Submitted by: Remcon
LOP 1.45
Author: Remcon
Submitted by: Remcon
LOP Heroes Edition
Author: Vladaar
Submitted by: Vladaar
Heroes sound extras
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.3
Author: Vladaar
Submitted by: Vladaar
Users Online
CommonCrawl, Yandex

Members: 0
Guests: 9
Stats
Files
Topics
Posts
Members
Newest Member
478
3,708
19,242
612
Jacki72H
Today's Birthdays
Evoru (32)
Related Links
» SmaugMuds.org » Codebases » AFKMud Support & Development » Hotboot stuff.
Forum Rules | Mark all | Recent Posts

Hotboot stuff.
< Newer Topic :: Older Topic > ...hotboot seg fault?

Pages:<< prev 1 next >>
Post is unread #1 Mar 6, 2003, 6:57 pm
Go to the top of the page
Go to the bottom of the page

Saiyr

GroupMembers
Posts3
JoinedMar 6, 2003

Yeah. I don't know if I need to e-mail you saying I used the snippet, Samson, but I e-mailed you like a year ago saying so, so hopefully you have that record. :P I tried installing a recent version of hotboot on a SMAUG 1.4a stock code. It worked, but it seems that whenever someone is creating or logging on, and it should kick them off, it crashes the MUD with a segmentation fault. Here's my backtrace:

#0 0x0809dd87 in do_hotboot (ch=Cannot access memory at address 0xbfffe010
) at comm.c:4420
Cannot access memory at address 0xbfffe008

Can I get some help? If not, I'll take about 8 years to figure it out. Thanks in advance.

--Saiyr
       
Post is unread #2 Mar 7, 2003, 12:33 pm
Go to the top of the page
Go to the bottom of the page

Guest - (Unregistered)

I tried installing a recent version of hotboot on a SMAUG 1.4a stock code. It worked, but it seems that whenever someone is creating or logging on, and it should kick them off, it crashes the MUD with a segmentation fault. Here's my backtrace:
#0 0x0809dd87 in do_hotboot (ch=Cannot access memory at address 0xbfffe010
) at comm.c:4420
Cannot access memory at address 0xbfffe008

I'm not Samson (I'd say thats potentially an advantage but someone will prolly thump me or worse *iwhis* ;) ), but I'll have a go anyway....

Firstly the backtrace isn't complete, I can't believe do_hotboot is the only stack item (if it is, something REALLY smashed the stack up), there should at least be calls below to game_loop among other things (although if not compiled with the right debug flags you can lack certain information..), but anywho..

The variable ch, appears to be invalid, be this through where the character was booted from the game as you said it should, or it was in the process of doing so and it never invalidated/removed the pointer from a list correctly. Either this or it was never initalised correctly and its hovering around randomly in memory and when you attempt to access it you get a wierd part of memory way outta your stack space and it goes boom

During the process of logging on/creating a character you exist as a descriptor up until a proper char_data is allocated and assigned, all I can think of at this point with the info you provided is that the pointers in the descriptor_data for those newer connections are not initalised to NULL correctly, and thus when it tries to access them it goes boom. While not having read the hotboot code (yet), most copyover/hotboot solutions work by filtering along the descriptor list and saving off the char_data info referred to by them, thus if a descriptor doesn't have a character it can't be restored.. if its not setup correctly, then this could screw everything up and crash it.

Firstly I'd recommend checking that during login/creation the descriptor_data is initalised correctly, there is usually a character field or similar inside the descriptor_data that MUST be set to NULL when the descriptor_data struct is created for use, failure to do so can result in the prog crashing like this.

Barring that, I'll go read the hotboot code, unless Samson gets back and provides a better and more complete answer
       
Pages:<< prev 1 next >>