 |
adamwalker
Apprentice
Joined: 12 Mar 2005
Posts: 195
|
 Posted: Wed Dec 13, 2006 5:46 am
[1.23] Crash on creation of module
|
create module
give it a name
click on an item in the directory viewer
date/time : 2006-12-13, 05:43:34, 468ms
computer name :
user name :
operating system : Windows XP Service Pack 2 build 2600
system language : English
system up time : 16 minutes 24 seconds
program up time : 1 minute 17 seconds
processors : 2x Intel(R) Pentium(R) 4 CPU 3.40GHz
physical memory : 150/511 MB (free/total)
free disk space : (C:) 122.97 GB
display mode : 1280x1024, 32 bit
process id : $17c
allocated memory : 34.98 MB
executable : CMUD.exe
exec. date/time : 2006-12-13 03:12
version : 1.23.0.0
madExcept version : 3.0b
contact name : adam walker
contact email :
callstack crc : $47a2947b, $160cfbdc, $160cfbdc
exception number : 1
exception class : EDatabaseError
exception message : MemSettings: Dataset is not in edit mode.
Main ($e48):
0063e96e +06a CMUD.exe DB 2350 +2 DatabaseError
00661bd2 +06a CMUD.exe kbmMemTable 10997 +5 TkbmCustomMemTable.SetFieldData
0064ecd3 +047 CMUD.exe DB 9224 +2 TDataSet.GetFieldData
0064ee03 +047 CMUD.exe DB 9250 +2 TDataSet.SetFieldData
005091b0 +034 CMUD.exe Controls 6237 +3 TWinControl.MainWndProc
0047f828 +014 CMUD.exe Classes 10966 +8 StdWndProc
00495fd8 +00c CMUD.exe SyncObjs 222 +1 TCriticalSection.Leave
0065bbd1 +009 CMUD.exe kbmMemTable 6033 +5 TkbmCommon.Unlock
00661b36 +23a CMUD.exe kbmMemTable 10887 +83 TkbmCustomMemTable.GetFieldData
0064ecd3 +047 CMUD.exe DB 9224 +2 TDataSet.GetFieldData
7c91096d +00c ntdll.dll RtlReleasePebLock
7c910942 +025 ntdll.dll RtlAcquirePebLock
7c91096d +00c ntdll.dll RtlReleasePebLock
7c90eae0 +010 ntdll.dll KiUserCallbackDispatcher
006428cf +08b CMUD.exe DB 4003 +4 TField.SetData
00644402 +06a CMUD.exe DB 4646 +4 TIntegerField.SetAsInteger
00d4702c +084 CMUD.exe ModuleFrame 122 +8 TModuleF.SaveScript
00d47075 +005 CMUD.exe ModuleFrame 134 +1 TModuleF.SaveSetting
00bf34fc +0b8 CMUD.exe PkgMain 1306 +10 TPkgMainF.SaveSetting
00a0848f +07b CMUD.exe DataSetHandler 178 +7 THandlerList.CallHandlers
00a08b9c +004 CMUD.exe DataSetHandler 284 +0 THandlerList.DoBeforePost
00651fb1 +021 CMUD.exe DB 10808 +1 TDataSet.DoBeforePost
006609dd +005 CMUD.exe kbmMemTable 10006 +1 TkbmCustomMemTable.DoBeforePost
0065117b +033 CMUD.exe DB 10256 +6 TDataSet.Post
00ac469c +0ac CMUD.exe cxDBData 4162 +16 TcxDBDataController.CheckBrowseMode
00ac5eb9 +081 CMUD.exe cxDBData 4890 +17 TcxDBDataController.TryFocusRecord
00ac3a0e +0d6 CMUD.exe cxDBData 3754 +20 TcxDBDataController.CanFocusRecord
005a8382 +03e CMUD.exe cxCustomData 6155 +4 TcxCustomDataControllerInfo.CanFocusedRowChanging
005a84de +07a CMUD.exe cxCustomData 6203 +10 TcxCustomDataControllerInfo.DoChangeFocusedRow
005aa4e5 +02d CMUD.exe cxCustomData 7368 +4 TcxCustomDataControllerInfo.SetFocusedRowIndex
005b0a14 +06c CMUD.exe cxCustomData 11260 +8 TcxCustomDataController.ChangeFocusedRowIndex
007e30c3 +03b CMUD.exe cxInplaceContainer 5354 +3 TcxCustomControlController.SetFocusedRecordIndex
007f3f25 +01d CMUD.exe cxTL 8016 +2 TcxTreeListController.SetFocusedRecordIndex
007e3455 +049 CMUD.exe cxInplaceContainer 5472 +5 TcxCustomControlController.SetFocusedRecordItem
007f6003 +01f CMUD.exe cxTL 8848 +2 TcxTreeListController.SetFocusedRecordItem
007e29fd +10d CMUD.exe cxInplaceContainer 5097 +20 TcxCustomControlController.DoMouseDown
007f504b +06f CMUD.exe cxTL 8456 +8 TcxTreeListController.DoMouseDown
007e54ff +077 CMUD.exe cxInplaceContainer 6800 +9 TcxEditingControl.MouseDown
00505be9 +091 CMUD.exe Controls 4728 +7 TControl.DoMouseDown
00505c4c +054 CMUD.exe Controls 4737 +5 TControl.WMLButtonDown
00560668 +0d8 CMUD.exe cxControls 2441 +15 TcxControl.WndProc
007e5706 +01e CMUD.exe cxInplaceContainer 6861 +3 TcxEditingControl.WndProc
005091b0 +034 CMUD.exe Controls 6237 +3 TWinControl.MainWndProc
0047f828 +014 CMUD.exe Classes 10966 +8 StdWndProc
77d496c2 +00a USER32.dll DispatchMessageA
0052e6f0 +0ac CMUD.exe Forms 6873 +13 TApplication.ProcessMessage
0052e737 +00f CMUD.exe Forms 6892 +1 TApplication.HandleMessage
0052e9d2 +0a6 CMUD.exe Forms 6976 +16 TApplication.Run
00d506cc +088 CMUD.exe CMUD 316 +17 initialization
7c91312f +069 ntdll.dll RtlUnicodeStringToAnsiString
7c812b94 +0b6 kernel32.dll GetVersionExA |
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Wed Dec 13, 2006 1:21 pm
|
No crash here. Are you running a fresh install rather than an upgrade?
|
|
|
|
|
Larkin
Wizard
Joined: 25 Mar 2003
Posts: 1113
Location: USA
|
Posted: Wed Dec 13, 2006 2:55 pm
|
I re-created this crash just the way adamwalker said, on a fresh installation of 1.23. Tried hitting the Save Changes button first, but it crashes on hitting the save button, too. When I closed CMUD, and then re-opened it with my session, the module was still there with the name I had given it.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Dec 13, 2006 6:29 pm
|
Not getting any crash here. Were you connected live to the MUD with triggers firing and stuff when you were doing this?
I assume when you say "click on an item in the directory viewer " that you mean to click on the "Untitled" window, since that's the only thing shown in the tree view after closing the session window and opening the settings editor. |
|
|
|
|
Larkin
Wizard
Joined: 25 Mar 2003
Posts: 1113
Location: USA
|
Posted: Wed Dec 13, 2006 6:44 pm
|
I did it with a brand new installation of version 1.23, in offline mode. I created a module, typed in the name, and hit the 'Save Changes' button, causing the exception. It only seems to happen when you actually open a session and not just hit ESC to get to the untitled window.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Dec 13, 2006 6:48 pm
|
OK, so exactly which session are you opening? I need the EXACT STEPS that you are using. I assume you are opening one of the predefined sessions? If you are opening one of your own sessions, then this is hardly a "new installation" and it's possible your session package is corrupted or something. But if it happens with one of the predefined sessions, let me know which one.
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Wed Dec 13, 2006 7:28 pm
|
Okay, so I did manage to reproduce this. Connect to the Aetolia session online. Click the Settings button to open the editor. Click New Module. Name it. Save. Boom.
Deleted the Data directory. Still happening. |
|
|
|
|
Larkin
Wizard
Joined: 25 Mar 2003
Posts: 1113
Location: USA
|
Posted: Wed Dec 13, 2006 8:18 pm
|
It happens with any of the predefined sessions, unmodified. I tested with Lusternia, Imperian, and Medievia. After three consistent failures, it's fairly safe to say that it doesn't matter which session you choose. Online/offline doesn't matter, either.
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Wed Dec 13, 2006 8:27 pm
|
It also happens with a new session (I just created one to a fictional address and tried it).
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Dec 13, 2006 9:02 pm
|
OK, verified. I have no idea why it requires having a session (since the Untitled *is* a session), but it's on the bug list.
|
|
|
|
|
|
|
|
