Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD General Discussion
meddlesome
Wanderer


Joined: 24 Aug 2012
Posts: 70

PostPosted: Mon Oct 01, 2012 11:15 am   

Automapper Access Violation when creating rooms that exist. [Resolved]
 
When I am using the automapper and I am cruising along drawing out the rooms and I get to a room say 2x2 or bigger, and I am drawing the rooms connected in a square, I will get this error if I move into a direction where there is a room, but I have not established a link from the direction I am cumming from.

To try and explain this better...

1 2
4 3

Say I start at 1, got to 2, then 3, then 4. If I move back to 1 to leave the room, since 1 has already been created I get this error, but I need that connection, so am I to stop every time and manually create a link that I can then cross without the error?

Code:
date/time         : 2012-10-01, 07:11:26, 515ms
operating system  : Windows XP Service Pack 3 build 2600
system up time    : 16 hours 35 minutes
program up time   : 9 minutes 21 seconds
processors        : 4x Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz
physical memory   : 2548/3317 MB (free/total)
free disk space   : (C:) 53.81 GB
display mode      : 1280x960, 32 bit
process id        : $a08
allocated memory  : 39.30 MB
executable        : cMUD.exe
exec. date/time   : 2008-10-31 13:09
version           : 2.37.0.0
compiled with     : BCB 2006/07
madExcept version : 3.0h
callstack crc     : $0143bdb0, $f8a9dc2a, $f8a9dc2a
exception number  : 1
exception class   : EAccessViolation
exception message : Access violation at address 00D1D2F1 in module 'cMUD.exe'. Read of address 00000018.

Main ($838):
00d1d2f1 +0775 cMUD.exe     MapNew    5844  +110 TNewMapF.Command
00cecaa6 +5922 cMUD.exe     MAIN     19271 +1005 HandleCase
00cf2d74 +00a0 cMUD.exe     MAIN     20292   +12 TMUDForm.ExecCommand
00d722a9 +00a9 cMUD.exe     CodeExec   952    +9 ExecMUDCommand
00d78270 +0454 cMUD.exe     CodeExec  2608   +45 DoDefault
00d7931b +0f2f cMUD.exe     CodeExec  2898  +274 HandleCom
00d7aa5e +060e cMUD.exe     CodeExec  3315  +108 TCodeExec.InternalExecute
00d713b6 +0072 cMUD.exe     CodeExec   520    +9 TCodeExec.Execute
00d78757 +036b cMUD.exe     CodeExec  2655   +31 HandleCom
00d7aa5e +060e cMUD.exe     CodeExec  3315  +108 TCodeExec.InternalExecute
00d71305 +0051 cMUD.exe     CodeExec   496    +8 TCodeExec.Execute
00d669ee +00c2 cMUD.exe     PrefDat  11325    +9 TCacheNode.Execute
00d62c5b +02ef cMUD.exe     PrefDat   9751   +52 PrefRec.InternalExecute
00d62eaa +0022 cMUD.exe     PrefDat   9808    +2 PrefRec.Execute
00cbdfdd +0151 cMUD.exe     MAIN      6636   +14 TMUDForm.ExecThread
00cbe295 +0015 cMUD.exe     MAIN      6683    +1 TMUDForm.ExecThread
00ccf680 +02cc cMUD.exe     MAIN     12786   +47 TMUDForm.ExecuteMacro
00cd0dcd +0a05 cMUD.exe     MAIN     13205  +180 TMUDForm.FormKeyDown
00c85366 +01b2 cMUD.exe     PARENT   11329   +20 TParentForm.BarShortCut
00c77fab +004b cMUD.exe     PARENT    3628    +6 CMUDKeyboardHook
7c90e470 +0010 ntdll.dll                         KiUserCallbackDispatcher
7e42a436 +00f6 USER32.dll                        PeekMessageA
004a960f +005f cMUD.exe     Forms                TApplication.ProcessMessage
004a96e6 +000a cMUD.exe     Forms                TApplication.HandleMessage
004a99db +00b3 cMUD.exe     Forms                TApplication.Run
00df80e0 +0088 cMUD.exe     CMUD       348   +20 initialization
7c9120d1 +0069 ntdll.dll                         RtlUnicodeStringToAnsiString
7c812c34 +00b6 kernel32.dll                      GetVersionExA
_________________
Intel Core 2 Quad Q9450 @2.66GHz
MDAC 2.8 SP1 ON WINDOWS XP SP3
Msjet40.dll ver 4.0.9511.0 + Security Bulletin MS08-028
CMUD v237
Order number: **7829

Last edited by meddlesome on Mon Oct 01, 2012 5:23 pm; edited 1 time in total
Reply with quote
Rahab
Wizard


Joined: 22 Mar 2007
Posts: 2320

PostPosted: Mon Oct 01, 2012 12:21 pm   
 
It should work automatically. It does for me. Most likely, one of your triggers is causing this. You are using triggers to #TAG
rooms, I believe? You can probably figure out which trigger is getting the exception by turning on the Debugger. I'm afraid that
I can't interpret the error output you posted, but perhaps someone else can, to help you track it down.
Reply with quote
meddlesome
Wanderer


Joined: 24 Aug 2012
Posts: 70

PostPosted: Mon Oct 01, 2012 12:49 pm   
 
Ok, that gives me something to work with. I do use Triggers to #TAG, so I'll start there. Thanks.
_________________
Intel Core 2 Quad Q9450 @2.66GHz
MDAC 2.8 SP1 ON WINDOWS XP SP3
Msjet40.dll ver 4.0.9511.0 + Security Bulletin MS08-028
CMUD v237
Order number: **7829
Reply with quote
meddlesome
Wanderer


Joined: 24 Aug 2012
Posts: 70

PostPosted: Mon Oct 01, 2012 5:23 pm   
 
I got this traced down to being an issue with #TAG exit. I slipped up and started using #TAG exits and that is not a valid tag.
_________________
Intel Core 2 Quad Q9450 @2.66GHz
MDAC 2.8 SP1 ON WINDOWS XP SP3
Msjet40.dll ver 4.0.9511.0 + Security Bulletin MS08-028
CMUD v237
Order number: **7829
Reply with quote
Rahab
Wizard


Joined: 22 Mar 2007
Posts: 2320

PostPosted: Mon Oct 01, 2012 6:55 pm   
 
Good work tracking that down!
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD General Discussion All times are GMT
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

© 2009 Zugg Software. Hosted by Wolfpaw.net