 |
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
 Posted: Sat Jun 28, 2008 3:48 pm
[2.29] Crash caused by flyout window
|
I did get an invalid pointer operation for the first crash. I could not replicate that exact error during my attempts at refining this procedure.
1. Launch CMud
2. Close Sessions window (ESC)
3. Enter at the command line #WIN test
4. Click the push pin on the test window to make it a flyout window
5. Open the Package Editor (CTRL-G)
6. Click on the 'test' window setting in the PE tree
7. Set its position to Tabbed, and click Save Changes
If you mess around with things for a while at this point you will notice there are all sorts of visual problems. Basically this is the step that seems to start messing things up.
8. Close the PE
9. Drag the untitled window to a floating position
| Code: |
date/time : 2008-06-28, 12:02:58, 565ms
user name : <admin>
operating system : Windows XP Service Pack 2 build 2600
system language : English
system up time : 19 days 15 hours
program up time : 37 seconds
processor : AMD Athlon(tm) Processor
physical memory : 130/383 MB (free/total)
free disk space : (C:) 11.84 GB
display mode : 1024x768, 32 bit
process id : $c94
allocated memory : 29.88 MB
executable : cMUD.exe
exec. date/time : 2008-06-25 16:17
version : 2.29.0.0
compiled with : BCB 2006/07
madExcept version : 3.0h
callstack crc : $30f4c55c, $f32aa8bf, $f32aa8bf
exception number : 1
exception class : EAccessViolation
exception message : Access violation at address 00702FF9 in module 'cMUD.exe'. Read of address 00000000.
Main ($13c4):
00702ff9 +015 cMUD.exe aqDocking 3406 +2 TaqInsideContainer.ResetTabControl
00701a34 +0b0 cMUD.exe aqDocking 2727 +10 TaqInsideContainer.DeleteChild
00711cba +02a cMUD.exe aqDockingBase 3216 +6 TaqCustomDockingControl.SetParentItem
00712a0c +040 cMUD.exe aqDockingBase 3586 +8 TaqCustomDockingControl.HideControl
00712be1 +0e9 cMUD.exe aqDockingBase 3646 +25 TaqCustomDockingControl.InternalRemoveFromDocking
00716eb6 +092 cMUD.exe aqDockingBase 6074 +9 TaqCustomDockingContainer.Destroy
00700584 +068 cMUD.exe aqDocking 2067 +10 TaqInsideContainer.Destroy
00404da4 +008 cMUD.exe System 21 +0 TObject.Free
007117a8 +000 cMUD.exe aqDockingBase 3067 +0 TaqCustomDockingControl.Release
007174b1 +009 cMUD.exe aqDockingBase 6278 +2 TaqCustomDockingContainer.Release
007173a4 +068 cMUD.exe aqDockingBase 6254 +12 TaqCustomDockingContainer.UpdateChildInfo
00718b88 +0c8 cMUD.exe aqDockingBase 7055 +21 TaqCustomDockingManager.UpdateTree
00718c77 +05f cMUD.exe aqDockingBase 7094 +12 TaqCustomDockingManager.EndUpdate
00712f62 +0c2 cMUD.exe aqDockingBase 3745 +16 TaqCustomDockingControl.MakeFloating
00704a4d +0f5 cMUD.exe aqDocking 4204 +25 TaqMover.EndDragging
006f8bfb +01f cMUD.exe aqDockingVS2005 801 +4 TaqVS2005Mover.EndDragging
0071b55a +03e cMUD.exe aqDockingBase 8541 +4 TaqCustomDockingFrame.MaskFormEndDrag
006e2a99 +021 cMUD.exe aqMaskForms 308 +4 TaqCustomMaskForm.DoEndDrag
006e2abb +01b cMUD.exe aqMaskForms 316 +4 TaqCustomMaskForm.EndDrag
0071b483 +043 cMUD.exe aqDockingBase 8518 +4 TaqCustomDockingFrame.HandleFrameMove
0071b5af +007 cMUD.exe aqDockingBase 8567 +1 TaqCustomDockingFrame.MaskFormMouseUp
006e2b6d +025 cMUD.exe aqMaskForms 348 +2 TaqCustomMaskForm.DoMouseUp
006e3488 +048 cMUD.exe aqMaskForms 716 +10 TaqTranslucentMaskForm.FormMouseUp
004bb93f +02b cMUD.exe Controls TControl.MouseUp
004bb978 +02c cMUD.exe Controls TControl.DoMouseUp
004bb9fa +076 cMUD.exe Controls TControl.WMLButtonUp
004bb06f +2bb cMUD.exe Controls TControl.WndProc
004bf073 +4fb cMUD.exe Controls TWinControl.WndProc
004a15d3 +553 cMUD.exe Forms TCustomForm.WndProc
004be79c +02c cMUD.exe Controls TWinControl.MainWndProc
0047c3e0 +014 cMUD.exe Classes StdWndProc
77d4bcc7 +00a USER32.dll DispatchMessageA
004a9748 +0fc cMUD.exe Forms TApplication.ProcessMessage
004a9782 +00a cMUD.exe Forms TApplication.HandleMessage
004a9a77 +0b3 cMUD.exe Forms TApplication.Run
00e4b7e0 +088 cMUD.exe CMUD 348 +20 initialization
7c91312f +069 ntdll.dll RtlUnicodeStringToAnsiString
7c812907 +0b6 kernel32.dll GetVersionExA |
|
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Sun Jun 29, 2008 7:47 pm
|
Confirmed. I didn't get to a crash, but I did see all the weird window stuff.
|
|
_________________
Asati di tempari! |
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Mon Jun 30, 2008 12:38 am
|
Tech, am I remembering right that you use CMudPro? There might be some small difference that would point out the flaw for Zugg. I doubt that there is any timing component to this crash, because I generated it consistently while reducing the steps, and then replicated it a second time with the perfected procedure.
|
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Mon Jun 30, 2008 2:32 am
|
Yeah Vijilante, I us CMudPro normally. If I recall correctly, Zugg the main differences were the SSH stuff and the built-in zMapper recognition.
|
|
_________________
Asati di tempari! |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Jul 01, 2008 5:19 pm
|
Added to bug list.
|
|
|
|
|
|
|
|
