BoundsChecker find/causes GPFs in MFC?
Lior Messinger -- 100274.2607@compuserve.com Monday, June 03, 1996 Platform: Win NT, VC++ 4.0 Hi all, I'm trying to use BoundsChecker (Numega Tech.) on an application built in MFC with ODBC usage. I getting unexplained GPFs, reported thru BoundsChecker, only when I run it under BoundsChecker. The errors are reported to happen in some MFC sources, and are quite inconsistent - sometimes it happens in CTL3D32-related area, sometimes in CNoTrackObject, CThreadSlotData.. etc. Sometimes they are Access Violations, soemtimes Program Faults. These errors happen only when I run the system with BoundsChecker. Has anyone heard of this problem? Any ideas? Thanks a lot for any info, Lior Messinger, Fundtech.
William Karp -- karpw@entire.com Tuesday, June 11, 1996 Lior Messinger wrote: > > Platform: Win NT, VC++ 4.0 > Hi all, > > I'm trying to use BoundsChecker (Numega Tech.) on an application built in MFC > with ODBC usage. I getting unexplained GPFs, reported thru BoundsChecker, only > when I run it under BoundsChecker. The errors are reported to happen in some MFC > sources, and are quite inconsistent - sometimes it happens in CTL3D32-related > area, sometimes in CNoTrackObject, CThreadSlotData.. etc. Sometimes they are > Access Violations, soemtimes Program Faults. These errors happen only when I run > the system with BoundsChecker. > Has anyone heard of this problem? Any ideas? > > Thanks a lot for any info, > Lior Messinger, Fundtech.I had some problems like this with Bounds checker for Win 3.11 with a Huge application (around 4 meg with debug info) Same here with the GPF's. For No reason, and in areas that never (and should never) have gpf's. To get rid of these problems, I removed some of the debugging checking that I was using. I haven't used BoundChecker in a little while, but it was a flag that made the debugging executable run real slow. I stopped checking for those problems, and it went away. I'd suggest just going into the options setup and setting some of them on and off. Maybe you can track down which flag it is that makes the GPF's. Also, is your symbol memory high enough. We had to put in a large value for ours. (I don't even know if BC for 32 bit needs symbol memory, but you can experiment with that Bill
Dave Kolb -- sasdxk@unx.sas.com Thursday, June 13, 1996 [Mini-digest: 2 responses] Sometimes normal operation of things like File Open dialogs generate GPF's during processing. Exception handlers in that code catch these and continue operation and so you normally never see them in your app. Perhaps this phenomena is what you are seeing??? Dave Kolb Dave Kolb Compuserve: 72410,407@compuserve.com SAS Institute, Inc. EMAIL: sasdxk@unx.sas.com SAS Campus Drive - R3282 Phone: (919) 677-8000 x6827 Cary, NC 27513-2414 USA FAX: (919) 677-8123 -----From: dobrin@itls.com Hi! The new BoundsChecker for NT, version 4.0, does not have these problems anymore. They removed even some of the annoying messages that were displayed previously and were not errors or warnings. But since the old days, setting on/off of some options will be advisable to test fully the behaviour of this new version. Dan Dobrin dan.dobrin@itls.com
| Вернуться в корень Архива |