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

#map goto problem with 2.00.8

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



Joined: 30 Dec 2011
Posts: 40

PostPosted: Sun Jan 15, 2012 8:36 am    Post subject: #map goto problem with 2.00.8 Reply with quote

I built the map with 2.00.5 and #map goto home worked fine. When I upgraded to 2.00.8, the same command causes a fault where tintin dies back to my shell prompt on Ubuntu 11.10 with:

DEBUG STACK[000] = find_room(0x8746110, home)

from my map:

dan@ubuntu:~/ourplace/tintin$ cat ourplace.map | grep home
R { 217} {0} {} {home} {SER} {roomnote-seraphim} {seraphim} {}

If I first do a #map goto 217 and then later do a #map goto home, it works fine. This worked under 2.00.5.
Back to top
View user's profile Send private message Send e-mail
Scandum
Site Admin


Joined: 03 Dec 2004
Posts: 3770

PostPosted: Sun Jan 15, 2012 12:05 pm    Post subject: Reply with quote

Thanks, fixed this in the beta:

http://tintin.sf.net/download/tintin-beta.tar.gz
Back to top
View user's profile Send private message Send e-mail
dandenison84



Joined: 30 Dec 2011
Posts: 40

PostPosted: Sun Jan 15, 2012 1:57 pm    Post subject: Reply with quote

Thanks, worked like a charm.
Back to top
View user's profile Send private message Send e-mail
RockyGryphon



Joined: 06 Mar 2012
Posts: 3

PostPosted: Fri Mar 16, 2012 10:11 am    Post subject: Reply with quote

I also built maps with 2.00.5, went to 2.00.8, had map problems and backed down to 2.00.7 until now it has been crashing when I go to a certain room (just a flash of red "debug" lines before it disappears and closes in windows xp sp3. Is there a windows version of this new beta or is a 2.00.9 coming out?

I haven't been able to compile in cygwin due to errors:
3 [main] gcc-4 2072 child_info_fork::abort: address space needed by 'cygiconv-2.dll' (0x6B310000) is already occupied
This repeats 8 times then:
gcc: vfork: Resource temporarily unavailable
Makefile:94: recipe for target `alias.o' failed
make: *** [alias.o] Error 1

I was able to compile another program (fontforge) so I know my installation of cygwin compiles.

(edit)
After running ./configure (in src), and make (both twice individually), I was able to get this compiled and installed (make install just once) so I guess I'll just use this beta in cygwin until a windows version comes out. Thanks for the beta... off to see how it does with my map (2650 rooms).
Back to top
View user's profile Send private message
RockyGryphon



Joined: 06 Mar 2012
Posts: 3

PostPosted: Fri Mar 16, 2012 12:13 pm    Post subject: Reply with quote

ok I appear to be getting the same error in 2.00.7, 2.00.8 in windows and cygwin. This problem just seemed to randomly appear and crash after using 2.00.7 for at least a few days if not a week. Here is the response I was able to copy out of cygwin after going one room away and attempting to do a #map goto 1 command which I have under an alias called, "home". nwm is the session name I believe.

DEBUG_STACK[000] = parse_input(nwm,home)
DEBUG_STACK[001] = parse_input(nwm,n)
DEBUG_STACK[002] = parse_input(nwm,go pub)
DEBUG_STACK[003] = parse_input(nwm,n)
DEBUG_STACK[004] = parse_input(nwm,go pub)
DEBUG_STACK[005] = parse_input(nwm,n)
DEBUG_STACK[006] = parse_input(nwm,go pub)
DEBUG_STACK[007] = parse_input(nwm,n)
DEBUG_STACK[008] = parse_input(nwm,go pub)
DEBUG_STACK[009] = parse_input(nwm,n)
DEBUG_STACK[010] = parse_input(nwm,go pub)
DEBUG_STACK[011] = parse_input(nwm,n)
DEBUG_STACK[012] = parse_input(nwm,go pub)
DEBUG_STACK[013] = parse_input(nwm,n)
DEBUG_STACK[014] = parse_input(nwm,go pub)
DEBUG_STACK[015] = parse_input(nwm,n)
DEBUG_STACK[016] = parse_input(nwm,go pub)
DEBUG_STACK[017] = parse_input(nwm,n)
DEBUG_STACK[018] = parse_input(nwm,go pub)
DEBUG_STACK[019] = parse_input(nwm,n)
DEBUG_STACK[020] = parse_input(nwm,go pub)
DEBUG_STACK[021] = parse_input(nwm,n)
DEBUG_STACK[022] = parse_input(nwm,go pub)
DEBUG_STACK[023] = parse_input(nwm,n)
DEBUG_STACK[024] = parse_input(nwm,go pub)
DEBUG_STACK[025] = parse_input(nwm,n)
DEBUG_STACK[026] = parse_input(nwm,go pub)
DEBUG_STACK[027] = parse_input(nwm,n)
DEBUG_STACK[028] = parse_input(nwm,go pub)
DEBUG_STACK[029] = parse_input(nwm,n)
DEBUG_STACK[030] = parse_input(nwm,go pub)
DEBUG_STACK[031] = parse_input(nwm,n)
DEBUG_STACK[032] = parse_input(nwm,go pub)
DEBUG_STACK[033] = parse_input(nwm,n)
DEBUG_STACK[034] = parse_input(nwm,go pub)
DEBUG_STACK[035] = parse_input(nwm,n)
DEBUG_STACK[036] = parse_input(nwm,go pub)

I'm thinking something on my end has changed to cause this all of a sudden, but I'm not sure what.
Back to top
View user's profile Send private message
RockyGryphon



Joined: 06 Mar 2012
Posts: 3

PostPosted: Fri Mar 16, 2012 3:05 pm    Post subject: Reply with quote

fixed it. it was under (I'm assuming) a great amount of sleep deprivation causing a symptom of stupidity involving the lack of memory in my head.

I had created the following alias:


#ALIAS {n}={go pub;w;u;bb;buy chili;buy chili;d;bb} @ {5}

and in conjunction with using a map (I think the alias may have actually worked until some point), saying go {to some room} caused the aforementioned result which was not always visible before a hard crash and exit in windows, but always visible in dos and cygwin. sorry. I'm back up working in 2.00.7 now. If I get brave I'll try 8, and iv even braver, attempt to port tintin++ to optware and run it 24/7 on my western digital my book world edition NAS that's been hacked with a mbwe feed. hahaha way off in the future though it would be awesome, then I could leave it on always with screen.

anyway, hopefully next time I'll remember to use some alias name other than a direction or exit like enter or south, etc. durrrhhh.
Back to top
View user's profile Send private message
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