Zugg Software :: View topic

Novice Joined: 15 Aug 2007 Posts: 39

Error Code 00DB86FC - 6d706876
43414268

Temporary trigger that is created by the mapper?

Pattern (Example, matches Roomnames): Intersection of Northwest Outer Rim and Eramyr Street
Body: #ok
Activated trigger prefs: Verbatim, Trigger on trigger, Trigger on Newline

- Error appears only when the package Editor is opened.
- Error Message appears very frequent (between every step and every 4 steps) while moving by keypad, mouse (on mapper)
- Does not appear while following with a move-on follow trigger

EDIT:

- You can circumvent this bug by disabling the systems folder and creating a trigger that sends an #ok message to the mud.
- Disabling the _Tempmap does not work, as it is recreated when you move.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Can you provide the exact text of the error message, or a screen shot of the error box. That looks like it might be within the range of the PCRE dll, and I would need the exact error to try to determine if my recent change to the dll or one of the other low level interface changes I made is causing this.

Novice Joined: 15 Aug 2007 Posts: 39

Sure:
The error ought to be from somewhere around 2.18 though - That is when I started reporting it but I did not know the source

Access violation at address 00DB86FC in module 'cMUD.exe'.
Read of address 6D706876

date/time : 2008-06-08, 00:26:38, 343ms
computer name : JALEN
user name : <admin>
registered owner :
operating system : Windows XP Service Pack 2 build 2600
system language : German
system up time : 3 hours 29 minutes
program up time : 1 hour 44 minutes
processors : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
physical memory : 1278/2047 MB (free/total)
free disk space : (C:) 5.39 GB (H:) 41.45 GB
display mode : 1280x1024, 32 bit
process id : $6dc
allocated memory : 223.95 MB
executable : cMUD.exe
exec. date/time : 2008-06-06 01:01
version : 2.26.0.0
compiled with : BCB 2006/07
madExcept version : 3.0h
contact name : Ghedemonas
contact email :
callstack crc : $8e13e184, $f74043d1, $f74043d1
exception number : 128
exception class : EAccessViolation
exception message : Access violation at address 00DB86FC in module 'cMUD.exe'. Read of address 6D706876.

Main ($770):
00db86fc +00b0 cMUD.exe PrefDat 11127 +10 TCacheNode.Execute
00db49e6 +024e cMUD.exe PrefDat 9565 +41 PrefRec.InternalExecute
00db4c2f +001f cMUD.exe PrefDat 9621 +2 PrefRec.Execute
00d121f5 +0151 cMUD.exe MAIN 6277 +14 TMUDForm.ExecThread
00d1ae9e +04d6 cMUD.exe MAIN 9082 +95 TMUDForm.ExecTrig
00d18908 +126c cMUD.exe MAIN 8284 +331 TMUDForm.HandleTrigger
00d17187 +000f cMUD.exe MAIN 7779 +1 TMUDForm.UserOutNewLine
00a59105 +0039 cMUD.exe term 8944 +3 TTerm.DoTriggerLine
00a57b08 +0218 cMUD.exe term 8514 +34 HandleNewLine
00a582fc +06e4 cMUD.exe term 8638 +104 TTerm.PutText
00a588bb +0053 cMUD.exe term 8744 +2 TTerm.Add
00d010ed +00b1 cMUD.exe MAIN 1601 +8 TMUDForm.OutputStr
00d013c2 +00d6 cMUD.exe MAIN 1682 +25 TMUDForm.NextMUDLine
00d01875 +0019 cMUD.exe MAIN 1759 +4 TMUDForm.DoNextLine
004bb077 +02bb cMUD.exe Controls TControl.WndProc
004bf07b +04fb cMUD.exe Controls TWinControl.WndProc
004a15db +0553 cMUD.exe Forms TCustomForm.WndProc
004be7a4 +002c cMUD.exe Controls TWinControl.MainWndProc
0047c3e8 +0014 cMUD.exe Classes StdWndProc
7e3696c2 +000a USER32.dll DispatchMessageA
004a9750 +00fc cMUD.exe Forms TApplication.ProcessMessage
004a978a +000a cMUD.exe Forms TApplication.HandleMessage
004a9a7f +00b3 cMUD.exe Forms TApplication.Run
00e487b4 +0088 cMUD.exe CMUD 350 +20 initialization
7c92312f +0069 ntdll.dll RtlUnicodeStringToAnsiString
7c812b94 +00b6 kernel32.dll GetVersionExA
0076006c +0018 cMUD.exe cxGroupBox 2750 +3 TcxCustomButtonGroup.CreateHandle

error details:
http://forums.zuggsoft.com/forums/viewtopic.php?p=132596#132596

SubAdmin Joined: 18 Nov 2001 Posts: 5182

After reviewing your detailed post I can say this is not a problem with the dll, but is something Zugg will have to review. Thank you for supplying the full crash dump. It makes a huge difference having those details.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Did Zugg do any work on room scripts yet? This sounds like something regarding that since 1)the System folder is no longer used anywhere except by the old mapper and 2)room triggers crash CMud.

Posted: Sun Jun 08, 2008 6:37 pm

There is also a tendency for "unclassed" settings to end up in the session window's System folder.

Posted: Mon Jun 09, 2008 5:47 pm

MattLofton is correct about this. This problem is caused by the fact that some Room Scripts can cause this crash. Your crash dump shows that some trigger is being executed based upon text received from the MUD and that this trigger is causing an error. So it might be because of a room script, but it also might be because of the temporary trigger created by CMUD to do the #OK command.

However, these are the issues that can't be fixed until I start working on the mapper stuff.

Magician Joined: 28 Jan 2007 Posts: 430

Same problem here. Went back to public version 2.37 and clean Package with only ansi triggers for #tagging name/exits/desc.
After little while, map doesn't track my location anymore and then I see System folder appearing, having _Tempmap folder inside
with some random trigger with body #OK I haven't even written.
Problem seemed to go away for a bit when I deleted all the rooms I had mapped so far but after, say 10 rooms it was back again and
map lost track of me.

Whole code here. Note once more, that the trigger with #OK isn't my doing.

Wizard Joined: 22 Mar 2007 Posts: 2320

Version 2.37 uses the old mapper. As noted, some room scripts and room-related triggers can cause problems like this. I am pretty sure it is fixed in the 3.xx mapper, since room scripts are completely changed in the beta version.