Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #4587

Re: Windows 7 memory corruption

From "Jamal" <vodotnet_nospam@yahoo.com>
Newsgroups comp.lang.clipper.visual-objects
Subject Re: Windows 7 memory corruption
Date 2013-01-15 16:44 -0500
Organization A noiseless patient Spider
Message-ID <kd4ij5$97v$1@dont-email.me> (permalink)
References <f4eb5757-b901-4e53-808a-907b44a1e679@googlegroups.com>

Show all headers | View raw


If it is critical to resolve the issue,  upgrading may be VO SP4 can help 
which has:

"A fix has been applied to the internal handling of dynamic memory to avoid 
a problem with the function DynProtect."

Of course there are many other fixes.

HTH,
Jamal

wrote in message 
news:f4eb5757-b901-4e53-808a-907b44a1e679@googlegroups.com...

Hi out there,

we have a rather big VO28SP2 application running at several client's sites 
and the clients are in the process of switching from WinXP to Windows 7. 
This went without big problems overall but I am trying to track down a 
certain problem which seems very evasive.

Clients report that the application crashes at some point and I can 
sometimes reproduce these crashes with Win7, even in the debugger. The crash 
looks like some sort of dynamic memory corruption (5333 for example at 
ADEDataWindow:Init() line 11, but only sometimes, and sometimes somewhere 
else).

It was like in the old days when we tried to fix the GPFs. I introduced some 
_DynCheck()/DynCheckError() calls and stepped through the code but I never 
was able to put my finger on the place where memory corruption might be 
caused. I placed those two function calls in the Watch Expressions at 
watched them, and at some point they did not show any results any longer. I 
tried DynLock() but the crash occurred anyway. The crash is not always 
logged as a 5333, sometimes the application simply stops working and Windows 
says the application does not work any longer.

The funny thing is that with XP everything is fine. At the moment it SEEMS 
that the problem also disappears when the application is running in Windows 
7 in XP compatibility mode but I'm not sure about that.

I'm running out of ideas. Anyone?

TIA
Kay-Vikor 

Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Windows 7 memory corruption kvstegemann@web.de - 2013-01-14 09:11 -0800
  Re: Windows 7 memory corruption D.J.W. van Kooten <public@ic2remove.this.com> - 2013-01-14 22:35 +0100
    Re: Windows 7 memory corruption kvstegemann@web.de - 2013-01-15 08:22 -0800
  Re: Windows 7 memory corruption Massimo Bighelli <info@arcasistemi.it> - 2013-01-15 18:23 +0100
  Re: Windows 7 memory corruption "Jamal" <vodotnet_nospam@yahoo.com> - 2013-01-15 16:44 -0500
    Re: Windows 7 memory corruption kvstegemann@web.de - 2013-01-16 05:06 -0800
      Re: Windows 7 memory corruption Karl Faller <k.faller_withoutthat_@onlinehome.de> - 2013-01-16 14:53 +0100
        Re: Windows 7 memory corruption kvstegemann@web.de - 2013-01-18 01:42 -0800
      Re: Windows 7 memory corruption "Jamal" <vodotnet_nospam@yahoo.com> - 2013-01-16 20:18 -0500
  Re: Windows 7 memory corruption Thomas <Thomas.Walter@ndstsk.de> - 2013-02-04 02:36 -0800

csiph-web