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

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD Beta Forum
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Thu Feb 11, 2010 4:54 pm   

Access Violation
 
I'm actually posting this for someone else. However, what would be causing the following error?

Access violation at address 009FFFD3 in module 'cMUD.exe'.
Write of address 00000004.

This is in 3.14a. They were trying to load a package of mine. I have the same OS and CPU they do and have no problems at all. It just crashes every time they try to load the package and for the life of me I cannot figure out why.

OS: Windows XP Pro
CPU: AMD Athlon 64 XP
Reply with quote
Arde
Enchanter


Joined: 09 Sep 2007
Posts: 605

PostPosted: Thu Feb 11, 2010 8:03 pm   
 
Try to get full crash info from them, especially call stack, and post it here.
_________________
My personal bug|wish list:
-Wrong Priority when copy-paste setting
-1 prompt trigger for Mapper, Session and General Options, not 3 different!
-#SECTION can terminate threads
-Buttons can't start threads
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Thu Feb 11, 2010 8:53 pm   
 
Yeah I was waiting on them to email.

Code:

user name         : user <admin>
registered owner  : user
operating system  : Windows XP Service Pack 3 build 2600
system language   : English
system up time    : 5 hours 30 minutes
program up time   : 1 hour 16 minutes
processors        : 2x AMD Athlon(tm) 64 X2 Dual-Core Processor TK-57
physical memory   : 1109/1918 MB (free/total)
free disk space   : (C:) 34.52 GB
display mode      : 1280x800, 32 bit
process id        : $f80
allocated memory  : 43.19 MB
executable        : cMUD.exe
exec. date/time   : 2010-02-08 13:53
version           : 3.14.0.1
compiled with     : BCB 2006/07
madExcept version : 3.0k
contact name      : *********
contact email     : ************
callstack crc     : $39f69f3d, $7e1f4031, $7e1f4031
count             : 2
exception number  : 4
exception class   : EAccessViolation
exception message : Access violation at address 009FFFD3 in module 'cMUD.exe'. Write of address 00000004.


Main ($a0c):
009fffd3 +003 cMUD.exe   chardat        2947  +1 TCharRec.Clear
00c7d9ae +00e cMUD.exe   PARENT         2141  +1 TParentForm.ClearSession
00c82d88 +08c cMUD.exe   PARENT         4308  +8 TParentForm.NewMUD
00c7ef66 +01a cMUD.exe   PARENT         2896  +2 MUDWindow
00c7f023 +093 cMUD.exe   PARENT         2914 +14 TParentForm.CharAction
00c7f0ca +006 cMUD.exe   PARENT         2943  +0 TParentForm.DoAction
004bc093 +2bb cMUD.exe   Controls                TControl.WndProc
004c0097 +4fb cMUD.exe   Controls                TWinControl.WndProc
004a25f7 +553 cMUD.exe   Forms                   TCustomForm.WndProc
00c2c064 +020 cMUD.exe   DXSounds       2128  +9 TCustomDXSound.FormWndProc
00c2a554 +00c cMUD.exe   DXClass         635  +1 TControlSubClass.WndProc
004bf7c0 +02c cMUD.exe   Controls                TWinControl.MainWndProc
0047d424 +014 cMUD.exe   Classes                 StdWndProc
7e42a993 +016 USER32.dll                         CallWindowProcA
00707a33 +0a7 cMUD.exe   aqDockingUtils 1728  +7 CallDefWndProc
00707b21 +0dd cMUD.exe   aqDockingUtils 1776 +41 TaqWindowEventFilter.WndProc
0047d424 +014 cMUD.exe   Classes                 StdWndProc
7e4196c2 +00a USER32.dll                         DispatchMessageA
004aa76c +0fc cMUD.exe   Forms                   TApplication.ProcessMessage
004aa7a6 +00a cMUD.exe   Forms                   TApplication.HandleMessage
004aaa9b +0b3 cMUD.exe   Forms                   TApplication.Run
00e27a78 +088 cMUD.exe   CMUD            352 +20 initialization
7c912c21 +069 ntdll.dll                          RtlUnicodeStringToAnsiString


It happens when adding the package to the session then opening session.
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Fri Feb 12, 2010 4:55 am   
 
It actually looks like something is wrong with their Sessions.db file (that is what the CharDat module handles). I don't really see it related to the actual package file itself. You might have them try renaming their Sessions.db and SessionKeys.db file and then create a brand new session to load the *.pkg file to see if that is the problem or not.
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD Beta Forum 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