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, Yahoo!, Google, Yandex

Members: 0
Guests: 3
Stats
Files
Topics
Posts
Members
Newest Member
478
3,708
19,242
612
Jacki72H
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Codebases » AFKMud Support & Development » Help Alarm
Forum Rules | Mark all | Recent Posts

Help Alarm
< Newer Topic :: Older Topic > BUG Haven't found on other forums

Pages:<< prev 1 next >>
Post is unread #1 Mar 5, 2005, 12:31 pm
Go to the top of the page
Go to the bottom of the page

Celestria

GroupMembers
Posts28
JoinedFeb 24, 2005

Everything was fine up to this point, then Everything went to garbage and all players got messed up and went linkdead, I had to reboot the mud. I'd like to get it fixed before it happens again, but when I grepped, alarm is all over the .c files, so i don't even know where to start.

Log: [*****] BUG: ALARM CLOCK! In section new_descriptor: after accept
Alas, the hideous malevalent entity known only as 'Lag' rises once more!
Log: clearing newdesc

[25000 25000 25000] 1200 just n3mComm:In com25000 nne0;37m: 24.34.118.225, el just n3mComm:IPreave one 0 at:n says m and disscussing their char with them is good enough. In the cases of paladiMax sm just n3mComm:ILve one 0 atn says (14K) just n3mComm:I says [24.34.118.225]y ask0 nne0;m[25000 25000 25000] 1200
ThMax sm just n3mLog: Vt1m
cliink d-------n says ;32m[says asketherwch hermYou. just n3mComm:I says
       
Post is unread #2 Mar 6, 2005, 11:18 am
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,639
JoinedJan 1, 2002

I have occasionally seen the descriptor alarm fire, but I haven't ever seen it cause the resulting buffer corruption you've got there. Usually it just drops the offending descriptor and that's the end of it. Without something more to go on, I'm not sure what to do about it.
       
Post is unread #3 Mar 6, 2005, 3:38 pm
Go to the top of the page
Go to the bottom of the page

Celestria

GroupMembers
Posts28
JoinedFeb 24, 2005

I haven't even a clue where to start with that one, code looks fine to me. No idea why it's doing that. I just hope it dosen't happen again. Is that particular alarm call essential to the code base or could I safely rem it out if it continues to cause problems?
       
Pages:<< prev 1 next >>