 |
Anaristos
Sorcerer
Joined: 17 Jul 2007
Posts: 821
Location: California
|
 Posted: Wed Dec 10, 2008 8:10 am
[237/302B] Catastrophic CMUD error
|
I can't explain what is going on, and it just started. I thought the problem was with the BETA version because it showed there first, but when I fell back on 2.37, it started happening there also. It always occurs while I am typing on the command line. I've tried sending the report but the transmission fails. So here it is:
| Code: |
date/time : 2008-12-09, 23:56:44, 23ms
computer name : XXXXXXXX
user name : XXXXXXXX <admin>
registered owner : XXXXXXXX
operating system : Windows Vista Service Pack 1 build 6001
system language : English
system up time : 4 hours 6 minutes
program up time : 2 hours 11 minutes
processors : 2x Intel(R) Core(TM) Duo CPU T2350 @ 1.86GHz
physical memory : 941/2037 MB (free/total)
free disk space : (C:) 46.64 GB
display mode : 1440x900, 32 bit
process id : $1364
allocated memory : 130.74 MB
executable : CMUDPro.exe
exec. date/time : 2008-10-31 09:10
version : 2.37.0.0
compiled with : BCB 2006/07
madExcept version : 3.0h
contact name : XXXXXXXX
contact email : XXXXXXXX
callstack crc : $b893b60c, $b2aaf088, $b2aaf088
exception number : 3
exception class : EAccessViolation
exception message : Access violation at address 008B5220 in module 'CMUDPro.exe'. Read of address 0000002C.
Main ($10a8):
008b5220 +004 CMUDPro.exe XpDOM 8049 +3 TXpElement.CreateChildElement
00e5e2a1 +0b5 CMUDPro.exe PkgDM 4318 +5 TPkg.AddOptionXML
00e5e4a3 +187 CMUDPro.exe PkgDM 4348 +19 TPkg.SetOptionXML
00e16e26 +122 CMUDPro.exe PrefDat 8293 +14 PrefRec.SetOption
00e2483c +058 CMUDPro.exe PrefDat 12827 +3 ButtonRec.SetTextCol
00e238de +04e CMUDPro.exe PrefDat 12614 +3 ButtonRec.FixColors
00e18447 +083 CMUDPro.exe PrefDat 8862 +6 ButtonRec.Invalidate
00d255da +92a CMUDPro.exe PARENT 4661 +195 TParentForm.UpdateButtons
00d228af +06f CMUDPro.exe PARENT 3420 +15 TParentForm.DoRefreshSetting
00d22906 +032 CMUDPro.exe PARENT 3434 +2 TParentForm.wmRefreshSetting
004bf29b +2bb CMUDPro.exe Controls 5146 +83 TControl.WndProc
004c329f +4fb CMUDPro.exe Controls 7304 +111 TWinControl.WndProc
004a57ff +553 CMUDPro.exe Forms 3512 +136 TCustomForm.WndProc
00cc4c4c +020 CMUDPro.exe DXSounds 2128 +9 TCustomDXSound.FormWndProc
00cc23f0 +00c CMUDPro.exe DXClass 635 +1 TControlSubClass.WndProc
004c29c8 +02c CMUDPro.exe Controls 7073 +3 TWinControl.MainWndProc
0047c4f0 +014 CMUDPro.exe Classes 11583 +8 StdWndProc
7794b9fc +016 USER32.dll CallWindowProcA
006d7e93 +0a7 CMUDPro.exe aqDockingUtils 1728 +7 CallDefWndProc
006d7f81 +0dd CMUDPro.exe aqDockingUtils 1776 +41 TaqWindowEventFilter.WndProc
0047c4f0 +014 CMUDPro.exe Classes 11583 +8 StdWndProc
77935a27 +00a USER32.dll DispatchMessageA
004ad974 +0fc CMUDPro.exe Forms 8105 +23 TApplication.ProcessMessage
004ad9ae +00a CMUDPro.exe Forms 8124 +1 TApplication.HandleMessage
004adca3 +0b3 CMUDPro.exe Forms 8223 +20 TApplication.Run
00eb1a1c +088 CMUDPro.exe cMUDPro 352 +20 initialization
7723490f +010 kernel32.dll BaseThreadInitThunk
error details:
Again, just typing on the command line. This is 2.37 though. I suspect it has to do with trigger processing.
|
Whatever it is, it is bad enough that it is keeping me from accessing the MUD because once it happens it will happen even when trying to open CMUD. Which points to package corruption. |
|
_________________
Sic itur ad astra. |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Dec 10, 2008 4:29 pm
|
Looks like something is causing one of your Buttons to get refreshed and the crash is happening when trying to access your button options. You might try disabling your buttons to track down which one is causing the problem. If you can narrow it down to something you can reproduce in a blank session, then I might be able to look into it more.
|
|
|
|
|
|
|
|
|
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
|
|
