TinTin++ Mud Client The TinTin++ message board

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
TinTin++ Mud Client

Odd crashes on #map find

 
Post new topic   Reply to topic    The TinTin++ message board Forum Index -> Bug Reports
View previous topic :: View next topic  
Author Message
ixle



Joined: 15 Sep 2011
Posts: 158
Location: United States

PostPosted: Thu Feb 16, 2012 5:02 am    Post subject: Odd crashes on #map find Reply with quote

Hrm, have had tintin crash twice when doing a #map find. I didn't record the debug info from the first one but here's the second:

DEBUG_STACK[000] = readmud(0x913e3b8) DEBUG_STACK[001] = [aard] do_one_line(the Evil Dark In the thick
DEBUG_STACK[002] = [aard] do_one_line(#END OF PATH.)

This happened fight after the map returned the "no path found" message. This room is in a "maze" area.

Oh, btw I never went to 2.00.8 full release because it was still having problems finding the correct paths for at least 1 area.
Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3796

PostPosted: Thu Feb 16, 2012 8:48 am    Post subject: Reply with quote

I think there's a post 2.00.8 beta with some map fixes, but not 100% sure.
Back to top
View user's profile Send private message Send e-mail
dandenison84



Joined: 30 Dec 2011
Posts: 40

PostPosted: Fri Feb 17, 2012 7:27 am    Post subject: Reply with quote

Might be related:

DEBUG_STACK[000] = readmud(0x84632a8)
DEBUG_STACK[001] = [.genae] do_one_line(The air is crisp and invigorating, the deciduous vegetation thinner than)

I have two characters, this one is following the other one. The other one did a #map run xyz. This one crashed about 1/2 way through the run. It doesn't happen all the time, maybe once per day.
Back to top
View user's profile Send private message Send e-mail
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3796

PostPosted: Fri Feb 17, 2012 6:09 pm    Post subject: Reply with quote

I need a sure way to reproduce the bug in order to look into it.

Looks like the crash originates in an action. What does the #END OF PATH. trigger look like?
Back to top
View user's profile Send private message Send e-mail
dandenison84



Joined: 30 Dec 2011
Posts: 40

PostPosted: Fri Feb 17, 2012 9:01 pm    Post subject: Reply with quote

I don't think i have an end of path trigger defined.
Back to top
View user's profile Send private message Send e-mail
ixle



Joined: 15 Sep 2011
Posts: 158
Location: United States

PostPosted: Sat Feb 18, 2012 12:59 am    Post subject: Reply with quote

In my case I can say that it happens when using a #map alias.

The alias is pretty involved, but basically it takes care of linking portals (#map dig), finding a vnum, room, or area (#map find), unlinking the portals (#map unlink), and running the path (#path run).
Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3796

PostPosted: Sun Feb 19, 2012 1:35 pm    Post subject: Reply with quote

I think I still have your map and script file, if you can give me more info I'll look into it.
Back to top
View user's profile Send private message Send e-mail
ixle



Joined: 15 Sep 2011
Posts: 158
Location: United States

PostPosted: Sat Feb 25, 2012 10:31 am    Post subject: Reply with quote

Code:
/* This isn't map related, but may be related anyway */

DEBUG_STACK[001] = [aard] do_one_line(You have 6 days, 22 hours and 15 minutes left to finish this campaign.)
DEBUG_STACK[002] = parse_input(aard,protocol gmcp sendchar)
DEBUG_STACK[003] = write_line_mud(0xbfea548c,0x8bdfc90)
DEBUG_STACK[004] = write_line_mud(0xbfea548c,0x8bdfc90)
DEBUG_STACK[005] = write_line_mud(0xbfea548c,0x8bdfc90)
DEBUG_STACK[006] = write_line_mud(0xbfea548c,0x8bdfc90)
DEBUG_STACK[007] = write_line_mud(0xbfea548c,0x8bdfc90)
DEBUG_STACK[008] = write_line_mud(0xbfea548c,0x8bdfc90)
DEBUG_STACK[009] = write_line_mud(0xbfea548c,0x8bdfc90)
DEBUG_STACK[010] = write_line_mud(0xbfea548c,0x8bdfc90)
DEBUG_STACK[011] = write_line_mud(0xbfea548c,0x8bdfc90)
DEBUG_STACK[012] = write_line_mud(0xbfea548c,0x8bdfc90)
broken_pipe: dumping stack



/* Typical One: This one has been repeating often with slight variations on the first few lines */
/* Upon further observation it looks like this happens when either a path is requested to the
/* area, room, or vnum I'm standing in, or when I bad search pattern is given.

/* In this example(#1), the movement is triggered off receiving a room name from a 'where <mobname>' command */
DEBUG_STACK[000] = readmud(0x86edcc0)
DEBUG_STACK[001] = [aard] do_one_line(the cell keeper      Passing Under Some Iron Gates)
DEBUG_STACK[002] = [aard] do_one_line(#END OF PATH.)

/* In this example(#2), an alias is used that finds a variable that matches a mob name, and tried to run to it's vnum */
DEBUG_STACK[000] = parse_input(aard,z)
DEBUG_STACK[001] = parse_input(aard,gototarg)
DEBUG_STACK[002] = parse_input(aard,vfind ${$targets[1][1]}[1][vnum])
DEBUG_STACK[003] = [aard] do_one_line(#END OF PATH.)

/* In this example(#3), A leftover action from example 1 tried to send a bad room name string */
DEBUG_STACK[000] = readmud(0x9d92cc0)
DEBUG_STACK[001] = [aard] do_one_line(A very young strolling minstrel is damned forever by the holy power!!)
DEBUG_STACK[002] = [aard] do_one_line(#END OF PATH.)
Back to top
View user's profile Send private message
ixle



Joined: 15 Sep 2011
Posts: 158
Location: United States

PostPosted: Sat Feb 25, 2012 1:03 pm    Post subject: Reply with quote

Totally new one, not even map related just on a #buffer find {mobs left}

Code:
DEBUG_STACK[000] = [aard] do_one_line(#BUFFER FIND, NO MATCHES FOUND.)
Back to top
View user's profile Send private message
ixle



Joined: 15 Sep 2011
Posts: 158
Location: United States

PostPosted: Tue Feb 28, 2012 2:00 am    Post subject: Reply with quote

Hrm I'm starting to get the idea these are all connected somehow.

Code:
DEBUG_STACK[000] = [aard] do_one_line(#PATH DEL: NO MOVES LEFT.)


This, as with all the rest, does not happen consistently. It is so far impossible for me to reproduce at will.
Back to top
View user's profile Send private message
ixle



Joined: 15 Sep 2011
Posts: 158
Location: United States

PostPosted: Tue Aug 14, 2012 10:29 pm    Post subject: Reply with quote

This one had some new info in it so I'll post it. I'm still getting these odd crashes when using some aliases for #map find.

Code:
DEBUG_STACK[000] = read_buffer_mud(0x86f8448)
DEBUG_STACK[001] = translate_telopts(0x86f8448,0xbfa9786c,429)
DEBUG_STACK[002] = recv_sb_gmcp(0x86f8448,1729,0x86ed098)
DEBUG_STACK[003] = goto_room(0x86f8448,30459)
DEBUG_STACK[004] = [aard] do_one_line(#END OF PATH.)
Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3796

PostPosted: Wed Aug 15, 2012 6:56 am    Post subject: Reply with quote

Looks like this one was triggered by a GMCP message.
Back to top
View user's profile Send private message Send e-mail
ixle



Joined: 15 Sep 2011
Posts: 158
Location: United States

PostPosted: Thu Oct 11, 2012 3:06 pm    Post subject: Reply with quote

Any news on this? I still get daily crashes with the red debug text when using #map find. Most often this happens when the find arguments match the current room.
Back to top
View user's profile Send private message
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3796

PostPosted: Sat Oct 13, 2012 6:28 am    Post subject: Reply with quote

It's on my TODO list. If you have a guaranteed way to reproduce the crash that'd be appreciated.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic   Reply to topic    The TinTin++ message board Forum Index -> Bug Reports All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Get TinTin++ Mud Client at SourceForge.net. Fast, secure and Free Open Source software downloads Get TinTin++ Mud Client at SourceForge.net. Fast, secure and Free Open Source software downloads
TinTin++ Homepage

Powered by phpBB © 2001, 2002 phpBB Group