Wierd MadExcept behaviour - bug??

delphi package - automated exception handling

Wierd MadExcept behaviour - bug??

Postby PhilA » Fri Jul 23, 2004 11:03 am

Sometimes when a bug report is trying to be generated it just hangs the software, sometimes you can see the bug report form but no buttons work etc. it has hung. Any ideas?

Here's an example of the later problem, clipboard bit still worked.

date/time : 2004-07-23 11:41
computer name : PHIL
user name : Philip
operating system : Windows XP Service Pack 1 build 2600
system language : English
system up time : 1 hour 46 minutes
program up time : 1 hour 40 minutes
processor : AMD Athlon(tm) XP 2700+
physical memory : 535/767 MB (free/total)
free disk space : (C:) 1.59 GB (Y:) 40.95 GB
display mode : 1024x768, 32 bit
process id : $a58
executable : Emat.exe
exec. date/time : 2004-07-22 10:38
version : 1.21.3.0
madExcept version : 2.7c beta 14
exception class : EExternalException
exception message : External exception C0000006.

main thread ($a5c):
>> internal error in CollectPossibleStackItems:
00413a48 ???
>> original exception location:
005b6c74 ???

thread $adc:
>> internal error in CollectPossibleStackItems:
00413a48 ???

thread $b94:
>> internal error in CollectPossibleStackItems:
>> created by main thread ($a5c) at:
00413a48 ???

modules:
00320000 vclx60.bpl Y:\Runtime\E-mat\Demo121
00400000 Emat.exe 1.21.3.0 Y:\Runtime\E-mat\Demo121
008a0000 ip4000v6.bpl Y:\Runtime\E-mat\Demo121
012f0000 mexhook.dll 3.4.2.22 D:\Macro Express3
01450000 HookDLL.DLL D:\Folder Cache
06330000 SSSensor.dll 5.5.0.5 C:\WINDOWS\System32
12170000 ACE32.DLL 6.20.0.11 Y:\Runtime\E-mat\Demo121
187b0000 axcws32.dll 6.20.0.0 Y:\Runtime\E-mat\Demo121
40000000 rtl60.bpl 6.0.6.240 Y:\Runtime\E-mat\Demo121
400b0000 vcl60.bpl 6.0.6.240 Y:\Runtime\E-mat\Demo121
40310000 dbrtl60.bpl 6.0.6.240 Y:\Runtime\E-mat\Demo121
40670000 vcldb60.bpl 6.0.6.240 Y:\Runtime\E-mat\Demo121
406e0000 bdertl60.bpl 6.0.6.163 Y:\Runtime\E-mat\Demo121
40860000 VclSmp60.bpl 1.0.0.0 Y:\Runtime\E-mat\Demo121
5ad70000 uxtheme.dll 6.0.2800.1106 C:\WINDOWS\System32
5edd0000 olepro32.dll 5.0.5014.0 C:\WINDOWS\System32
70a70000 SHLWAPI.dll 6.0.2800.1400 C:\WINDOWS\system32
71950000 comctl32.dll 6.0.2800.1106 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.10.0_x-ww_f7fb5805
71a50000 mswsock.dll 5.1.2600.0 C:\WINDOWS\system32
71a90000 wshtcpip.dll 5.1.2600.0 C:\WINDOWS\System32
71aa0000 WS2HELP.dll 5.1.2600.0 C:\WINDOWS\System32
71ab0000 WS2_32.dll 5.1.2600.0 C:\WINDOWS\System32
71ad0000 wsock32.dll 5.1.2600.0 C:\WINDOWS\System32
71b20000 mpr.dll 5.1.2600.0 C:\WINDOWS\system32
73000000 winspool.drv 5.1.2600.1106 C:\WINDOWS\System32
732e0000 RICHED32.DLL 5.1.2600.0 C:\WINDOWS\System32
74d30000 oledlg.dll 5.1.2600.0 C:\WINDOWS\System32
74e30000 RICHED20.DLL 5.30.23.1211 C:\WINDOWS\System32
75e90000 SXS.DLL 5.1.2600.1106 C:\WINDOWS\System32
76390000 imm32.dll 5.1.2600.1106 C:\WINDOWS\System32
763b0000 comdlg32.dll 6.0.2800.1106 C:\WINDOWS\system32
76400000 msi.dll 2.0.2600.1106 C:\WINDOWS\System32
76b40000 winmm.dll 5.1.2600.1106 C:\WINDOWS\System32
76f20000 DNSAPI.dll 5.1.2600.1106 C:\WINDOWS\System32
76f60000 WLDAP32.dll 5.1.2600.1106 C:\WINDOWS\system32
76f90000 Secur32.dll 5.1.2600.1106 C:\WINDOWS\System32
76fb0000 winrnr.dll 5.1.2600.0 C:\WINDOWS\System32
76fc0000 rasadhlp.dll 5.1.2600.0 C:\WINDOWS\System32
77050000 COMRes.dll 2001.12.4414.42 C:\WINDOWS\System32
77120000 oleaut32.dll 3.50.5016.0 C:\WINDOWS\system32
771b0000 OLE32.DLL 5.1.2600.1362 C:\WINDOWS\system32
77340000 comctl32.dll 5.82.2800.1106 C:\WINDOWS\system32
773d0000 SHELL32.dll 6.0.2800.1233 C:\WINDOWS\system32
77c00000 version.dll 5.1.2600.0 C:\WINDOWS\system32
77c10000 MSVCRT.DLL 7.0.2600.1106 C:\WINDOWS\system32
77d40000 user32.dll 5.1.2600.1255 C:\WINDOWS\system32
77dd0000 ADVAPI32.dll 5.1.2600.1106 C:\WINDOWS\system32
77e60000 kernel32.dll 5.1.2600.1106 C:\WINDOWS\system32
77f50000 ntdll.dll 5.1.2600.1217 C:\WINDOWS\System32
78000000 RPCRT4.dll 5.1.2600.1361 C:\WINDOWS\system32
7c890000 CLBCATQ.DLL 2001.12.4414.53 C:\WINDOWS\System32
7e090000 GDI32.dll 5.1.2600.1346 C:\WINDOWS\system32
PhilA
 
Posts: 10
Joined: Mon May 10, 2004 7:58 am

Postby madshi » Sat Jul 24, 2004 9:28 pm

Did you start the application from a network drive? These "external exceptions" usually occur if somehow the exe gets ripped off its own feet. It seems that the whole process is in big problems.
madshi
Site Admin
 
Posts: 10200
Joined: Sun Mar 21, 2004 5:25 pm

Postby PhilA » Mon Jul 26, 2004 7:44 am

I know external exceptions are windows related etc. I more interested in why on occasion the bug report is not showing, my app just locks up. This was just an example on one instance when it occurred. Thanks.
PhilA
 
Posts: 10
Joined: Mon May 10, 2004 7:58 am

Postby madshi » Mon Jul 26, 2004 7:52 am

There can be 3 reasons:

(1) There might be a bug in madExcept.

(2) Or your process might be in such a wild state that madExcept can't properly do its work anymore. E.g. if the memory manager doesn't work reliably, madExcept can't work reliably, either.

(3) Or Windows might have lost contact to the exe file somehow. This can happen if the exe was started from a network/CD/USB-drive. If the medium on which the exe is stored goes away (for whatever reason) or the connection to the volume is not stable, things like "EExternalException" can occur. In that case madExcept will run into problems, as well.

The bug report you posted above lets me believe that this specific situation was (3). But I can only guess here.
madshi
Site Admin
 
Posts: 10200
Joined: Sun Mar 21, 2004 5:25 pm

Postby PhilA » Mon Jul 26, 2004 8:06 am

Thanks. I'll keep an eye out for it happening again. I'll try and get other bug report errors.
PhilA
 
Posts: 10
Joined: Mon May 10, 2004 7:58 am


Return to madExcept

Who is online

Users browsing this forum: No registered users and 14 guests