IsBadReadPtr (4.0.12)

delphi package - automated exception handling
Post Reply
doug.stewart
Posts: 2
Joined: Wed Apr 06, 2016 3:46 pm

IsBadReadPtr (4.0.12)

Post by doug.stewart »

When setting madExcept to handle exceptions, we receive a madExcept error with log (I'm not allowed by the message board to attach it it seems):

Code: Select all

date/time          : 2016-03-10, 12:29:06, 165ms
computer name      : TQM-W07-A1
user name          : FcSrvBuild <admin>
registered owner   : fcsrvbuild
operating system   : Windows 7 x64 Service Pack 1 build 7601
system language    : English
system up time     : 1 day 9 hours
program up time    : 10 minutes 9 seconds
processors         : 2x Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz
physical memory    : 890/3610 MB (free/total)
free disk space    : (C:) 24.41 GB (D:) 28.81 GB
display mode       : 1280x1024, 16 bit
process id         : $be0
allocated memory   : 217.08 MB
largest free block : 250.56 MB
executable         : Flowcal.exe
current module     : madExcept_.bpl
exec. date/time    : 2016-03-10 12:00
version            : 8.11.33.966
compiled with      : Delphi XE7
madExcept version  : 4.0.12
contact name       : doug
contact email      : none@flowcal.com
callstack crc      : $fe2ed1f3, $0da41896, $6fd22ee8
exception number   : 1
exception class    : Unknown
exception message  : Unknown.

main thread ($1258):
76add0ac +0037 kernel32.dll                                                                    IsBadReadPtr
778a0137 +002b ntdll.dll                                                                       KiUserCallbackDispatcher
7557075c +0192 USER32.dll                                                                      PeekMessageW
5071627c +0014 vcl210.bpl            Vcl.Forms                                      10331   +2 TApplication.ProcessMessage
50716386 +000a vcl210.bpl            Vcl.Forms                                      10374   +1 TApplication.ProcessMessages
005489ba +000a FCExtendedEditors.bpl FcObjectSelector.cpp                             701   +2 TFcObjectSelector.SetPropertiesAfterObjectTypeSelect
005487cb +04a3 FCExtendedEditors.bpl FcObjectSelector.cpp                             654  +63 TFcObjectSelector.SetItemType
0054931c +015c FCExtendedEditors.bpl FcObjectSelector.cpp                             972  +26 TFcObjectSelector.SetAllowedTypesSet
00546efe +21b2 FCExtendedEditors.bpl FcObjectSelector.cpp                             395 +301 TFcObjectSelector.Create
We do not receive any issues unless madExcept is turned on to handle exceptions. This is currently breaking our smoke tests, and until we figure it out we have had to turn madExcept off.

Research from prior posts suggest that at one point there were calls to IsBadReadPtr in the hooks of madExcept, but it was later discussed that is no longer the case. My understanding is that IsBadReadPtr is a deprecated function that had many issues with it, but I am unsure as to how to address it. Is there a way to force madExcept to ignore this exception type?
madshi
Site Admin
Posts: 10754
Joined: Sun Mar 21, 2004 5:25 pm

Re: IsBadReadPtr (4.0.12)

Post by madshi »

Can you please double check whether the problem still occurs with 4.0.14? If so, please post another bug report from 4.0.14, thanks.
doug.stewart
Posts: 2
Joined: Wed Apr 06, 2016 3:46 pm

Re: IsBadReadPtr (4.0.12)

Post by doug.stewart »

After upgrading to 4.0.14, our Smoke Tests have been able to run successfully 6 continuous times. We are going to show this as an implicit indication that the upgrade has resolved the issue.

Thanks.
madshi
Site Admin
Posts: 10754
Joined: Sun Mar 21, 2004 5:25 pm

Re: IsBadReadPtr (4.0.12)

Post by madshi »

Good to hear!
Post Reply